Digital credentials as guest check-in for physical building access

ABSTRACT

A system for credential authentication includes an interface and a processor. The interface is configured to receive a create indication to create a guest credential representing a guest badge associated with a visitor and receive a claim indication from an authentication device to claim the guest credential. The processor is configured to provide the guest credential to the authentication device in response to the claim indication, provide a proof request to the authentication device, receive a proof response from the authentication device, validate the proof response, determine a visitor tracking system associated with a request from the authentication device to authenticate entry, and provide a check-in indication to the visitor tracking system that the visitor has checked in.

CROSS REFERENCE TO OTHER APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/648,854 entitled SYSTEM FOR ISSUANCE, VERIFICATION, ANDREVOCATION OF CREDENTIALS filed Mar. 27, 2018 which is incorporatedherein by reference for all purposes. This application also claimspriority to U.S. Provisional Patent Application No. 62/798,387 entitledDIGITAL CREDENTIALING ACCESS MANAGEMENT filed Jan. 29, 2019 which isincorporated herein by reference for all purposes. This application alsoclaims priority to U.S. Provisional Patent Application No. 62/798,389entitled DIGITAL CREDENTIALING PRIMARY FACTOR AUTHENTICATION filed Jan.29, 2019 which is incorporated herein by reference for all purposes.This application also claims priority to U.S. Provisional PatentApplication No. 62/798,391 entitled DIGITAL CREDENTIALING PRIMARY FACTORAUTHENTICATION FOR A PHYSICAL DEVICE filed Jan. 29, 2019 which isincorporated herein by reference for all purposes. This application alsoclaims priority to U.S. Provisional Patent Application No. 62/798,393entitled DIGITAL CREDENTIALING SECONDARY FACTOR AUTHENTICATION filedJan. 29, 2019 which is incorporated herein by reference for allpurposes. This application also claims priority to U.S. ProvisionalPatent Application No. 62/798,397 entitled DIGITAL CREDENTIALING STEP-UPAUTHENTICATION filed Jan. 29, 2019 which is incorporated herein byreference for all purposes. This application also claims priority toU.S. Provisional Patent Application No. 62/798,398 entitled DIGITALCREDENTIALING FOR ACCESS OF SENSITIVE DATA filed Jan. 29, 2019 which isincorporated herein by reference for all purposes. This application alsoclaims priority to U.S. Provisional Patent Application No. 62/798,400entitled DIGITAL CREDENTIALING FOR EMPLOYEE BADGE filed Jan. 29, 2019which is incorporated herein by reference for all purposes. Thisapplication also claims priority to U.S. Provisional Patent ApplicationNo. 62/798,402 entitled DIGITAL CREDENTIALING FOR GUEST CHECK-IN FORPHYSICAL BUILDING ACCESS filed Jan. 29, 2019 which is incorporatedherein by reference for all purposes. This application also claimspriority to U.S. Provisional Patent Application No. 62/798,403 entitledSEAMLESS AND SECURE WIFI ACCESS WITH VISITOR CREDENTIALS filed Jan. 29,2019 which is incorporated herein by reference for all purposes. Thisapplication also claims priority to U.S. Provisional Patent ApplicationNo. 62/798,404 entitled LOCATION AWARE CHECKIN filed Jan. 29, 2019 whichis incorporated herein by reference for all purposes. This applicationis also a continuation of co-pending U.S. patent application Ser. No.16/021,234 entitled REQUESTING CREDENTIALS filed Jun. 28, 2018 which isincorporated herein by reference for all purposes, which claims priorityto U.S. Provisional Application No. 62/648,854 entitled SYSTEM FORISSUANCE, VERIFICATION, AND REVOCATION OF CREDENTIALS filed Mar. 27,2018 which is incorporated herein by reference for all purposes. Thisapplication is also a continuation of co-pending U.S. patent applicationSer. No. 16/021,240 entitled SHARING CREDENTIALS filed Jun. 28, 2018which is incorporated herein by reference for all purposes, which claimspriority to U.S. Provisional Application No. 62/648,854 entitled SYSTEMFOR ISSUANCE, VERIFICATION, AND REVOCATION OF CREDENTIALS filed Mar. 27,2018 which is incorporated herein by reference for all purposes. Thisapplication is also a continuation of co-pending U.S. patent applicationSer. No. 16/021,243 entitled IDENTIFYING REVOKED CREDENTIALS filed Jun.28, 2018 which is incorporated herein by reference for all purposes,which claims priority to U.S. Provisional Application No. 62/648,854entitled SYSTEM FOR ISSUANCE, VERIFICATION, AND REVOCATION OFCREDENTIALS filed Mar. 27, 2018 which is incorporated herein byreference for all purposes.

BACKGROUND OF THE INVENTION

A database system distributes cryptographic digital credentials to auser to allow the user to prove qualifications (e.g., a degree,employment experience, health insurance coverage, etc.). Credentials canbe assigned to a user by a trusted third party client of the databasesystem (e.g., a university, an insurer). Digital credentials can be usedto authenticate building check-in for a guest, however, usingcredentials for authentication requires a system designed to use thecredentials securely.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1A is a block diagram illustrating an embodiment of a networksystem.

FIG. 1B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 1C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service.

FIG. 1D is a flow diagram illustrating an embodiment of a process forcreating an identity mapping on a distributed ledger.

FIG. 1E is a flow diagram illustrating an embodiment of a process forresponding to a proof request challenge.

FIG. 1F is a flow diagram illustrating an embodiment of a process forproviding a proof request.

FIG. 2A is a diagram illustrating an embodiment of a system forcredential storing and verifying using a distributed ledger.

FIG. 2B is a diagram illustrating an embodiment of a DCIAMS.

FIG. 2C is a diagram illustrating an embodiment of a holder device.

FIG. 2D is a diagram illustrating an embodiment of a distributed ledger.

FIG. 2E is a diagram illustrating an embodiment of a credential.

FIG. 2F is a diagram illustrating an embodiment of a presentation.

FIG. 2G is a flow diagram illustrating a process for credential storingand verifying using a distributed ledger.

FIG. 2H is a flow diagram illustrating an embodiment of a process forstoring a document on a distributed ledger.

FIG. 2I is a flow diagram illustrating an embodiment of a process forverifying a credential.

FIG. 3A is a block diagram illustrating an embodiment of a networksystem.

FIG. 3B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 3C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 3D is a flow diagram illustrating an embodiment of a process forauthenticating a login.

FIG. 3E is a flow diagram illustrating an embodiment of a process forcredential based app authorization.

FIG. 3F is a flow diagram illustrating an embodiment of a process fordetermining a uniform record identifier using a QR code process.

FIG. 3G is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 3H is a flow diagram illustrating an embodiment of a process for adigital identity application.

FIG. 4A is a block diagram illustrating an embodiment of a networksystem.

FIG. 4B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 4C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service.

FIG. 4D is a block diagram illustrating an embodiment of a user system.

FIG. 4E is a flow diagram illustrating an embodiment of a process foraccessing a network application.

FIG. 4F is a flow diagram illustrating an embodiment of a process forsigning in using a proximity authentication device challenge.

FIG. 4G is a flow diagram illustrating an embodiment of a process forcredential based authorization.

FIG. 4H is a flow diagram illustrating an embodiment of a process forproviding a session keypair and authentication token to a user device.

FIG. 4I is a flow diagram illustrating an embodiment of a process for acredential challenge.

FIG. 4J is a flow diagram illustrating an embodiment of a process for adigital identity application.

FIG. 4K is a flow diagram illustrating an embodiment of a process forproviding an authentication token.

FIG. 5A is a block diagram illustrating an embodiment of a networksystem.

FIG. 5B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 5C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 5D is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 5E is a flow diagram illustrating an embodiment of a process for adigital identity application.

FIG. 5F is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 6A is a block diagram illustrating an embodiment of a networksystem.

FIG. 6B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 6C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 6D is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 6E is a flow diagram illustrating an embodiment of a process forproviding a challenge to a user authentication device.

FIG. 6F is a flow diagram illustrating an embodiment of a process fordetermining whether a response is valid.

FIG. 6G is a flow diagram illustrating an embodiment of a process fordetermining whether a response is valid.

FIG. 6H is a flow diagram illustrating an embodiment of a process forresponding to a signature challenge.

FIG. 6I is a flow diagram illustrating an embodiment of a process forresponding to a credential challenge.

FIG. 6J is a flow diagram illustrating an embodiment of a process for anapplication system.

FIG. 7A is a block diagram illustrating an embodiment of a networksystem.

FIG. 7B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 7C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 7D is a block diagram illustrating an embodiment of an applicationsystem.

FIG. 7E is a block diagram illustrating an embodiment of a user system.

FIG. 7F is a flow diagram illustrating an embodiment of a process forproviding access.

FIG. 7G is a flow diagram illustrating an embodiment of a process for anauthentication device.

FIG. 7H is a flow diagram illustrating an embodiment of a process for anapplication system.

FIG. 7I is a flow diagram illustrating an embodiment of a process for auser system.

FIG. 8A is a block diagram illustrating an embodiment of a networksystem.

FIG. 8B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 8C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 8D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credentialing.

FIG. 8E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication.

FIG. 8F is a flow diagram illustrating an embodiment of a process forunlocking a lock.

FIG. 8G is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 8H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 9A is a block diagram illustrating an embodiment of a networksystem.

FIG. 9B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 9C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 9D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication.

FIG. 9E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication.

FIG. 9F is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 9G is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 9H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 10A is a block diagram illustrating an embodiment of a networksystem.

FIG. 10B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 10C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 10D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication.

FIG. 10E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication.

FIG. 10F is a flow diagram illustrating an embodiment of a process foraccessing a network.

FIG. 10G is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 10H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 10I is a flow diagram illustrating an embodiment of a process forauthenticating network access.

FIG. 11A is a block diagram illustrating an embodiment of a networksystem.

FIG. 11B is a block diagram illustrating an embodiment of anauthentication device.

FIG. 11C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS).

FIG. 11D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication.

FIG. 11E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication.

FIG. 11F is a flow diagram illustrating an embodiment of a process forcheck in.

FIG. 11G is a flow diagram illustrating an embodiment of a process forcredential authentication.

FIG. 11H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid.

FIG. 11I is a flow diagram illustrating an embodiment of a process forproviding a location specific message.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

The system for digital credentialing is designed to empower individualusers to own their verifiable professional identity and to be able toenable this identity to be useable in scenarios where a verifiedidentity allows access by providing proof of identity. An applicationmight use the system to prove the identity or verify a user's accessability to something. The application queries the system regarding aproof of identity and the user provides the proof using a credential tothe system that is ultimately passed to the application to proveidentity of the user. The system allows an application developer to pickattributes that an application challenges for and the sources that willsatisfy any given challenge. The proof of identity is embodied in adigital credential that is able to be secured using a combination ofcryptography and a distributed ledger (e.g., a decentralized ledger, apermissioned ledger, a public ledger, etc.) to assure legitimacy of theproof of identity.

A system for digital credentialing receives the digital credential froma credential issuing system. The system for digital credentialing storesuser information for the user. The system for digital credentialingfurther determines a set of credentials available to the user based onthe user information as well as stores a record of previously issuedcredentials. The credentials comprise categories satisfied by the userinformation at differing levels of specificity (e.g., greater than anamount, in a range of amounts, less than an amount, etc.). For example,in the case where the user comprises an employee earning $95,000 peryear, the system for digital credentialing could determine credentialsavailable to the user indicating that the user earns more than $60,000per year, that the user earns more than $80,000 per year, that the userearns in the range of $90,000-$100,000 per year, etc. When the userinteracts with the system for digital credentialing using a credentialrequesting app or application, the system determines the set ofcredentials available to the user and provides the list of credentialsto the credential requesting app or application. The user can thenprovide (e.g., from a storage on a user device) one or more availablecredentials to the credential requesting app or application.

In various embodiments, a credential comprises data that is validated orverified to be authentic—for example, data verifying academic diplomas,academic degrees, certifications, security clearances, identificationdocuments, badges, passwords, user names, keys, powers of attorney,human resource data, personal information, or any other relevantinformation,

When a user indicates to provide a credential, a credential is providedto the system for digital credentialing. The system determines whetherthe credential is valid for the user, and in the event the credential isvalid for the user, the system provides it to the application to proveidentity and enable access. By enabling the transfer of personalinformation between disparate database systems using authenticatedcredentials, this system allows that transfer of information with alevel of trust and security not previously accomplished. This allows thereduction or elimination of problems such as data theft duringinformation transfer and misrepresentation of personal information.

The system is a better computer system enabling efficient secure proofof identity and enablement of access. For example, the system is set upto securely receive and provide credentials. The security protocols andthe distributed ledger storage enable the credentials to act as atrusted source. The credentials can then be used to provide access orprove identity enabling a system to trust the user. In the disclosedbelow, example use cases and/or example applications are described fordigital credentials.

Case A—Digital Credential Authentication

A system for creating an identity mapping on a distributed ledgercomprises an interface configured to receive a request to create anidentity mapping on a distributed ledger, and a processor configured togenerate an identity key pair, generate a mobile encryption key, encrypta private identity key of the identity key pair using the mobileencryption key to create an encrypted private key, store the encryptedprivate key, create a mapping document, sign the mapping document withthe private identity key of the identity key pair, and provide thesigned mapping document to be stored in a distributed ledger.

A system for creating an identity mapping on a distributed ledgercomprises an authentication device in communication with a distributedledger (e.g., a permissioned ledger, a public ledger, a decentralizedledger, a blockchain, etc.). The identity mapping enables being able tosecurely and verifiably provide credentials from a user's authenticationdevice to a requestor (e.g., a requesting application). Theauthentication device comprises a computing device (e.g., a computer, asmartphone, a tablet, etc.). For example, the authentication devicecomprises a mobile computing device. An identity mapping comprises amapping from a user identifier to an authentication device public key.For example, an authentication device public key comprises a public keyof an identity key pair (IKP) of the authentication device. The IKPcomprises a public key and a private key (e.g., a public identity keyand a private identity key). The public key is public (e.g., publiclyknown and shared widely) and the private key is private (e.g., knownonly to the authentication device as a carefully guarded secret).Another system can securely send data to the authentication device byencrypting the data using the authentication device public key. It canthen only be decrypted using the authentication device private key(e.g., it can only be decrypted by the authentication device).Conversely, if the authentication device can sign data by encrypting thedata using the authentication device private key. The authenticationdevice private key cannot be recovered from the signed data, however,the signed data can be decrypted using the authentication device publickey (e.g., proving that the signed data comes from the authenticationdevice). Storing a mapping in a distributed ledger from a useridentifier to a public key value comprises a method of publicizing thepublic key value in a trusted way and of indicating that the user is ingood standing.

The authentication device creates an IKP comprising a public key and aprivate key. For example, the IKP is generated using an RSA algorithm oran ed25519 algorithm. A mapping document is created (e.g., according tothe world wide web consortium decentralized identifier (DID) documentspecification). For example, the mapping document maps a user identifierto the authentication device public key value. In some embodiments, theuser identifier comprises a public key. In some embodiments, the useridentifier is a random value and the mapping document points to thecurrent public key associated with this value—this enables key rotation.In some embodiments, the form of the mapping doc includes four sectionsor key/value pairs: 1) an identifier key/value pair, 2) a JSON-LDreference which designates the schema for the doc, 3) the public keybeing registered, and 4) an agent endpoint that other parties can use todiscover or interact with. The mapping document is then signed using theauthentication device private key and submitted to a decentralizedledger for storage. For example, a permissioned writer of thedecentralized ledger receives the mapping document, verifies that theauthentication device is a trusted source, and adds the mapping documentto the decentralized ledger. In some embodiments, the mapping documentincludes a decentralized identifier. The authentication device thensecurely stores the IKP private key. For example, the authenticationdevice generates a mobile encryption key that is securely stored on theauthentication device (e.g., using dedicated hardware for securelystoring mobile encryption key data). In some embodiments, the encryptionkey is stored in a secure enclave like a hardware security module (HSM)that the mobile encryption key data cannot leave. The IKP private key isencrypted using the mobile encryption key and only the encrypted IKPprivate key is stored. Decrypting the encrypted IKP private key requiresaccess to the mobile encryption key, which is access limited, forexample, using a biometric.

FIG. 1A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 1A comprises anetwork system for a database processing system. In the example shown,FIG. 1A comprises network 1A00. In various embodiments, network 1A00comprises one or more of the following: a local area network, a widearea network, a wired network, a wireless network, the Internet, anintranet, a storage area network, or any other appropriate communicationnetwork. Authentication device 1A02, distributed ledger 1A04, digitalcredential aware identity and access management service (DCIAMS) 1A06,and data base system 1A08 communicate via network 1A00. Authenticationdevice 1A02 comprises an authentication device associated with a user(e.g., a user of database system 1A08). For example, authenticationdevice 1A02 comprises a computer, a smartphone, a tablet, a mobiledevice, etc. Distributed ledger 1A04 comprises a distributed ledger(e.g., a blockchain). For example, distributed ledger 1A04 is stored ona plurality of systems and comprises one or more permissioned writersystems for writing to the distributed ledger. DCIAMS 1A06 comprises asystem for interacting with authentication device 1A02, distributedledger 1A04, database system 1A08, and any other appropriate systems.DCIAMS 1A06 comprises a system for coordinating a login for databasesystem 1A08, for providing a credential to authentication device 1A02,for requesting a credential from authentication device 1A02, forverifying a user identifier or a signature in distributed ledger 1A04,etc. Database system 1A08 comprises a system for executing a databaseapplication, storing database data, requesting database data, creating areport based on database data, creating a document, accessing adocument, etc. In some embodiments, DCIAMS 106 helps to protectapplication systems other than database systems.

Authentication device 1A02 comprises a system for creating an identitymapping on a distributed ledger (e.g., on distributed ledger 1A04). Forexample, authentication device 1A02 comprises a system for receiving arequest to create an identity mapping on a distributed ledger,generating an IKP, generating a mobile encryption key, encrypting aprivate identity key of the IKP using the mobile encryption key tocreate an encrypted private key, storing the encrypted private key,creating a mapping document, signing the mapping document with theprivate identity key of the IKP, and providing the signed mappingdocument to be stored in a distributed ledger.

FIG. 1B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 1B00of FIG. 1B comprises authentication device 1A02 of FIG. 1A. In theexample shown, authentication device 1B00 comprises interface 1B02. Forexample, interface 1B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 1B04comprises a processor for executing applications 1B06. Applications 1B06comprises digital identity application 1B08 and any other appropriateapplications. Digital identity application 1B08 comprises an applicationfor creating an identity mapping on a distributed ledger. For example,digital identity application 1B08 comprises an application forgenerating an IKP, generating a mobile encryption key, encrypting aprivate identity key of the IKP using the mobile encryption key tocreate an encrypted private key, storing the encrypted private key,creating a mapping document, signing the mapping document with theprivate identity key of the IKP, and providing the signed mappingdocument to be stored in a distributed ledger. Digital identityapplication 1B08 additionally comprises an application for receiving aproof request challenge, determining a set of stored digitalcredentials, determining a subset comprising the credentials of a set ofstored digital credentials that satisfy the proof request challenge,providing a user interface for allowing a user to select a digitalcredential of the subset that satisfies the proof request challenge,providing a proof response comprising the selected digital credential,and proof of control of said credential through a digital signature. Insome embodiments, the proof response comprises a signed verifiable formof the digital credential. In some embodiments, processor 1B04 isconfigured to install digital identity application 1B08 (e.g., uponreceiving an indication to install the digital identity application).

Secure enclave 1B10 comprises a secure system for storing a mobileencryption key. Secure enclave 1B10 comprises mobile encryption key 1B12and encryption decryption application 1B14. For example, secure enclave1B10 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave1B10 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave1B10 is configured to only provide transformed input data and not toprovide mobile encryption key 1B12. In some embodiments, functionalityof secure enclave 1B10 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) or a personalidentification number (PIN) to protect enclave access. Authenticationdevice 1B00 additionally comprises storage 1B16. Storage 1B16 comprisesencryption keys 1B18, for example comprising a public key of an identitykey pair, a private key of an identity key pair, a private key of anidentity key pair encrypted using mobile encryption key 1B12, etc.Storage 1B16 additionally comprises digital credentials 1B1B0,comprising digital certificates representing qualifications (e.g., acollege degree, work experience, time living at an apartment, timeenrolled in a health insurance plan, etc.). Authentication device 1B00additionally comprises memory 1B22. Memory 1B22 comprises executingapplication data 1B24, comprising data associated with applications1B06.

FIG. 1C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (e.g., aDCIAMS). In some embodiments, DCIAMS 1C00 comprises DCIAMS 1A06 of FIG.1A. In the example shown, DCIAMS 1C00 comprises interface 1C02. Forexample, interface 1C02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 1C04comprises a processor for executing applications 1C06. Applications 1C06comprise a set of DCIAMS applications. Decryption application 1C08comprises an application for coordination with an end-user device toselectively decrypt information that is encrypted with IPK keys. Loginapplication 1C10 comprises an application for receiving logininformation (e.g., username and password, a credential, a QR codechallenge, etc.) and providing login credentials (e.g., a login token).Login application 310 delegates to token generation application 316 togenerate a token based on a successful login interaction. Ledgerinterface application 1C12 comprises an application for interacting witha distributed ledger (e.g., distributed ledger 104 of FIG. 1). Forexample, ledger interface application 1C12 comprises an application forverifying a signature in a ledger or checking a credential identifierfor revocation in a ledger. Proof request application 1C14 comprises anapplication for creating a proof request, sending a proof request,evaluating a proof request response (e.g., a proof response), etc. Tokengeneration application 1C16 comprises an application for generating alogin token (e.g., in response to a successful login). Credentialissuing application 1C18 comprises an application for issuing a digitalcredential for proving a qualification (e.g., a user qualification) inresponse to a request from a credential issuing authority to issue thecredential. Applications 1C06 additionally comprises any otherappropriate applications.

Storage 1C20 comprises user and device database 1C22 and credentialrules 1C24. User and device database 1C22 comprises a database ofregistered users for a given customer organization and user details(e.g., username, password hash, contact information, email address,relationship to devices, registered public keys, registered mappingdocuments in a decentralized ledger, etc.). User and device database1C22 additionally comprises a device directory comprising all thedevices for a given customer organization as well as mapping documentsassociated with the devices and relationships with users associated withthe devices. Credential rules 1C24 comprises a set of credential rulesfor determining one or more credentials that are needed to satisfy agiven access request—for example, rules related to a credentialassociated schema, a credential associated organization, a credentialissuer, a credential associated location, a credential associated classidentifier, a credential associated license number, or any otherappropriate credential rules. DCIAMS 1C00 additionally comprises memory1C26. Memory 1C26 comprises executing application data 224, comprisingdata associated with applications 206.

FIG. 1D is a flow diagram illustrating an embodiment of a process forcreating an identity mapping on a distributed ledger. In someembodiments, the process of FIG. 1D is executed by digital identityapplication 1B08 of FIG. 1B. In the example shown, in 1D00, a request isreceived to create an identity mapping on a distributed ledger. In 1D02,an identity key pair is generated. In 1D04, a mobile encryption key isgenerated. In 1D06, a private identity key of the IKP is encrypted usingthe mobile encryption key to create an encrypted private key. In 1D08,the encrypted private key is stored. In 1D10, a mapping document iscreated. In 1D12, the mapping document is signed with the privateidentity key of the IKP. In 1D14, the signed mapping document isprovided to be stored in a distributed ledger. In some embodiments,providing the signed mapping document to be stored in a distributedledger comprises providing the signed mapping document to a permissionedwriter for the distributed ledger. In 1D16, it is determined whether asigned mapping document was valid when received. For example, the DCIAMSdetermines whether the signed mapping document was valid when receivedat the distributed ledger by receiving an indication that the signedmapping document passed a validation check performed by the distributedledger prior to being stored in the ledger (e.g., was validated bychecking the signature of the mapping document). In some embodiments, afurther indication is received from the distributed ledger indicatingthat the signed mapping document was successfully accepted to be storedand confirmed to be stored in the distributed ledger

FIG. 1E is a flow diagram illustrating an embodiment of a process forresponding to a proof request challenge. In some embodiments, theprocess of FIG. 1E is executed by digital identity application 1B08 ofFIG. 1B. In the example shown, in 1E00, a proof request challenge isreceived, wherein the proof request challenge comprises a request forone or more digital credentials, wherein the one or more digitalcredentials are determined using rules. In 1E02, a set of stored digitalcredentials is determined. In 1E04, a subset comprising the credentialsof the set of stored digital credentials that satisfy the proof requestchallenge is determined. In 1E06, a user interface is provided forallowing a user to select a digital credential of the subset thatsatisfies the proof request challenge. In 1E08, a proof response isprovided comprising the selected digital credential. For example, theone or more selected digital credentials are provided in response to therequest, where the proof response is signed using the IKP private key toprove that is was generated by the holder of the credential and alsoincludes timestamp to show liveness (e.g., that the proof response hasnot expired or is stale).

FIG. 1F is a flow diagram illustrating an embodiment of a process forproviding a proof request. In some embodiments, the process of FIG. 1Fis executed by proof request application 1C14 of FIG. 1C. In the exampleshown, in 1F00, an indication is received to provide a proof request. In1F02, one or more digital credentials that satisfy the proof request aredetermined, wherein the one or more digital credentials are determinedusing rules. For example, rules comprise rules related to a credentialassociated schema, rules related to a credential associatedorganization, rules related to a credential issuer, rules related to acredential associated location, rules related to a credential associatedclass identifier or identifier number, rules related to a credentialassociated license or license number, a credential associated classname, or any other appropriate credential rules. In some embodiments,the rules are applied selectively (e.g., based at least in part on auser identifier)—for example, employees with a credential can accessapplication A, contractors with a credential can access application B,or any other appropriate matching of access with identifiers. In variousembodiments, the rules are applied selectively based at least in part oncurrent employment, employee type, location of user, qualification bytraining class, credential from a third party issuer (e.g., division ofmotor vehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked); In some embodiments, selectiveapplication of rules combined with credential based authorization andsingle sign-on access control enable effective and configurablesecurity. In 1F04, the proof request is created, comprising a requestfor one or more digital credentials. In 1F06, the proof request isprovided.

A system for creating an identity mapping on a distributed ledgercomprises an interface and a processor. The interface is configured toreceive a request to create an identity mapping on a distributed ledger.The processor is configured to generate an identity key pair; generate amobile encryption key; encrypt a private identity key of the identitykey pair using the mobile encryption key to create an encrypted privatekey; store the encrypted private key; create a mapping document; signthe mapping document with the private identity key of the identity keypair; and provide the signed mapping document to be stored in adistributed ledger. In some embodiments, the processor is configured toinstall a digital identity application. In various embodiments, theidentity key pair comprises a public identity key, a private identitykey, an identity key pair generated using an RSA algorithm, an identitykey pair generated using an ed25519 algorithm, or any other appropriatekey pair. In some embodiments, mobile encryption key is stored in asecure enclave. In some embodiments, the mobile encryption key is accesslimited using a biometric. In some embodiments, the encrypted privatekey is stored in a user device (e.g., a mobile device). In someembodiments, the mapping document comprises a decentralized identifier.In some embodiments, the mapping document conforms to a World Wide WebConsortium decentralized identifier document specification. In someembodiments, the mapping document maps a user identifier to a public keyvalue or the user identifier comprises a public key. In someembodiments, the processor is further configured to receive anindication that the signed mapping document was validated. In someembodiments, the distributed ledger comprises a blockchain. In someembodiments, the signed mapping document is provided to a permissionedwriter for the distributed ledger. In some embodiments, the systemcomprises a storage for storing a digital credential for proving a userqualification. In some embodiments, the processor is configured toprovide a proof response comprising a signed verifiable form of thedigital credential in response to a proof request challenge. In someembodiments, the proof request challenge comprises a request for one ormore digital credentials wherein the one or more digital credentials aredetermined according to rules. In various embodiments, the rules areassociated with a credential schema, a credential organization, acredential issuer, a credential location, a credential class identifier,a credential class name, a credential issuer, an identification numberassociated with the credential, a license associated with thecredential, or any other associated credential data. In someembodiments, the rules are applied selectively. In some embodiments, therules are applied based at least in part on a user identifier.

Case B—Credential Storing and Verifying using a Distributed Ledger

A system for credential storing and verifying using a distributed ledgeris disclosed. The system includes an interface and a processor. Theinterface is configured to receive an indication to register acredential. The processor is configured to indicate to store in adistributed ledger a decentralized identifier (DID) document associatedwith a holder identifier using a smart contract, wherein storing usingthe smart contract employs a dual signature authentication scheme toauthorize storing based at least in part on an individual signature anda ledger writer signature;; indicate to store in the distributed ledgera schema associated with an issuer of the credential using the smartcontract; and indicate to store in the distributed ledger a credentialdefinition associated with the schema using the smart contract.

The system for credential storing and verifying using a distributedledger is used by the system to check a credential that is being used toestablish identity or legitimacy. A server system acts to intermediatebetween a requestor requesting a credential and a user holding acredential. The server system is able to verify the legitimacy of thecredential as the credential, a pointer to the credential (e.g., anidentifier), other related information (e.g., a decentralized identifierdocument), and/or information about the credential are stored in adistributed ledger by the issuer (e.g., an encryption/decryption key fora stored credential) and can be used as a check for the credential. Thisdistributed ledger is accessible by the server system. The distributedledger enables secure storage using a smart contract module that is runby each of the distributed ledger nodes. The smart contract ensures thatthe request to store an item on the distributed ledger is performed byan authorized user and by an authorized writer (e.g., by having therequest and/or requested item be signed by the authorized user and bythe authorized writer). In addition, smart contract module is designedto check a schema associated with the issuer of the credential, acredential definition associated with the schema, a decentralizedidentifier (DID) document associate with a holder identifier associatedwith a holder of a credential, and/or a DID document associated with anissuer of the credential.

In some embodiments, the system provides an item to the distributedledger and the smart contract determines whether there is a signaturefailure (e.g., a signature of the user, a signature of the writer, orany other relevant a signature). In some embodiments, the smart contractdetermines whether there is a uniqueness failure (e.g., that the item tobe stored is not already stored in the distributed ledger). In someembodiments, the smart contract determines whether there the storage inthe distributed ledger was successful. In the event that a failure tostore the item was detected, the smart contract module indicates thefailure to the requestor to store the item (e.g., a server system thathas requested that the item is to be stored in the distributed ledger).In the event that a storage success was detected, an indication isprovided to the requestor to store the item that the item wassuccessfully stored.

In some embodiments, the smart contract module verifies that acredential is valid by checking the credential against informationstored in the distributed ledger. In some embodiments, the request forverifying the credential is also checked to make sure that it isappropriately signed—for example, with the signature of an appropriaterequestor, the signature of a credential holder, the signature of arequestor, etc.). The smart contract modules determine whether theschema and the credential definition match stored information related tothe schema and stored information related to the credential definitionin the distributed ledger. In the event that a failure to validate thecredential is detected, the smart contract module indicates to therequestor that the credential is not valid. In the event that thecredential is validated using information stored in the distributedledger, then a revocation database is checked (e.g., as stored by thesmart contract module) to see whether the credential has been revokedand in the event it has not been revoked the requestor for validation isprovided an indication that the credential is valid and not revoked. Inthe event that the credential is revoked, then the requestor is providedan indication that the credential is revoked.

The system makes a computer better by improving the ability to providesecure access. The system provides for checks ensuring that a writer anduser are allowed to write to a distributed ledger and that an item to bestored is valid and unique and is successfully stored. The systemfurther provides checks to validate a credential with stored informationon the distributed ledger including schema information, credentialdefinition information, as well as DID documents related to a holder andan issuer of a credential. The system therefore allows for making thesystem more secure by providing secure access to appropriate users basedon a verifiable and trustworthy credential.

FIG. 2A is a diagram illustrating an embodiment of a system forcredential storing and verifying using a distributed ledger. In theexample shown, issuer 2A00 provides identity information to digitalcredential aware identity and access management service (DCIAMS) 2A04that is a permissioned writer/reader to distributed ledger 2A08. DCIAMS2A04 is able to store received and signed information from issuer 2A00.This information can include identity information (e.g., a decentralizedidentifier) or credential information (e.g., a schema for a credentialor a credential). Issuer 2A00 also provides a user the credential tohold in holder device 2A02. When a user uses the credential forestablishing proof of identity or the validity of information, a requestcan be made to verify the credential—requestor 2A06 contacts DCIAMS 2A04to verify a credential presented by a user using holder device 2A02.DCIAMS 2A04 is able to verify the credential by checking the credentialagainst information placed in distributed ledger 2A08. In variousembodiments, a credential schema, the credential itself, and arevocation table that are stored by issuer 2A00 on distributed ledger2A08 can be used to check that a credential is legitimate. DCIAMS 2A04can then provide requestor 2A06 with a verification that the credentialsupplied by a user held on holder device 2A02.

FIG. 2B is a diagram illustrating an embodiment of a DCIAMS. In someembodiments, DCIAMS 2B00 of FIG. 2B is used to implement DCIAMS 2A04 ofFIG. 2A. In the example shown, issuer interface 2B02 receives a DIDdocument, a credential schema, a credential definition, a credential, orany other appropriate information from an issuer and provides theinformation to processor 2B14. Issuing module 2B08 of processor 2B14indicates to a distributed ledger via distributed ledger interface 2B16to write the information received from the issuer. The distributedledger performs checking prior to storing on the distributed ledgerincluding possibly checking a signature of the information, checking asignature associated with the writer, and/or ensuring that theinformation is unique compared to previously stored information on thedistributed ledger. Holder device interface 2B04 receives a DID documentor any other appropriate information from a holder device and providesthe information to processor 2B14. Holding module 2B10 of processor 2B14indicates to a distributed ledger via distributed ledger interface 2B16to write the information received from holder device. Requestorinterface 2B06 receives a request from a requestor to verify acredential that a user wishes to use to establish identity or to enableaccess or prove validity. Verifying module 2B12 indicates to distributedledger via distributed ledger interface 2B16 to verify the credential.The distributed ledger performs checking to verify the credentialincluding possibly checking the schema of the credential, checking thecredential itself, and/or checking a revocation table to determinewhether the credential has been revoked. In some embodiments, holderdevice presents credential information directly to DCIAMS 2B00 inresponse to a verification request regarding the credential from therequestor.

FIG. 2C is a diagram illustrating an embodiment of a holder device. Insome embodiments, holder device 2C00 of FIG. 2C is used to implement2A02 of FIG. 2A. In the example shown, DID information provider 2C06 ofprocessor 2C12 provides DID information (e.g., an identifier or DIDdocument) to be stored on a distributed ledger via network interface2C14 and a network to a server (e.g., DCIAMS) that has permission towrite/read to the distributed ledger. Holder device 2C00 also receives acredential and stores the information in secure memory 2C02. In someembodiments, credential receiver 2C08 of processor 2C12 handles thereceipt of a credential from an issuer via network using networkinterface 2C14. In some embodiments, the release of information insecure memory 2C02 requires a biometric, a separate additional password,a personal identification number, a two-factor authentication, or anyother appropriate security measure. In some embodiments, holder devicecomprises a smart phone. Holder device 2C00 also provides a presentationusing presentation provider 2C10 of processor 2C12 to a server. Theserver is able then to request verification of the credential usinginformation stored in a distributed ledger. Memory 2C04 is available toprocessor 2C12 to store instructions or other information useful for theoperation of holder device 2C00.

FIG. 2D is a diagram illustrating an embodiment of a distributed ledger.In some embodiments, distributed ledger 2D00 of FIG. 2D is used toimplement distributed ledger 2A08 of FIG. 2A. In the example shown,distributed ledger 2D00 receives information to write and read on ledger2D02 using smart contract 2D09. Smart contract 2D09 comprises a softwaremodule that is installed in distributed ledger 2D00 that is executed tocustomize interactions for the system with ledger 2D02—for example,reading from the ledger and writing to the ledger are mediated by thesmart contract that is configured to check signatures, check uniqueness,check that storage proceeded correctly, check schema of a credentialwith stored information, check a credential definition of a credentialwith stored information, and/or check whether a credential is on arevocation list (e.g., where the revocation list is stored in orassociated with smart contract 2D09, For example, information isreceived from a network via network interface 2D12 and written to ledger2D02 using ledger writer 2D06 of processor 2D10 or information isprovided to the network via network interface 2D12 after being read fromledger 2D02 using ledger reader 2D08 of processor 2D10. In some cases,ledger 2D02 stores DID documents, credential schema, credentialdefinitions, or any other appropriate information. In some embodiments,information is checked to make sure that its one or more signaturesis/are valid and/or it is unique and has not previously been stored onledger 2D02 prior to being stored on ledger 2D02. In some cases ledger2D02 is read to obtain DID documents, credential schema, credentialdefinitions, revocation information, or any other appropriateinformation that can be used to verify that a credential is valid.

FIG. 2E is a diagram illustrating an embodiment of a credential. In someembodiments, the credential of FIG. 2E is stored on distributed ledger2A08 of FIG. 2A. In the example shown, the credential includes issuer2E00—for example, a uniform resource identifier or a decentralizedidentifier (DID). Issuer 2E00 as shown is defined ashttps://dmv.example.gov. Credential also includes holder DID 2E02.Holder DID 2E02 as shown is defined as“did:example:ebfeb1f712ebc6f1c276e21ec12”. Credential also includesclaim data 2E04 (e.g., “age”: 21). Credential information can alsoinclude an algorithm (e.g., RS256″), a type (e.g., “JWT”), an issue date(e.g., 2010-01-01), a verifiable credential type (e.g.,ProofOfAgeCredential), an expiration date (e.g., 2030-01-01), or anyother appropriate information.

FIG. 2F is a diagram illustrating an embodiment of a presentation. Insome embodiments, the presentation is presented to a DCIAMS (e.g.,DCIAMS 2A04 of FIG. 2A) in order to request verification of acredential. In the example shown, the presentation includes holder DID2F00 (e.g., “did:example:76e12ec21ebhyu1f712ebc6f1z2”). The presentationalso includes issuer DID 2F02 (e.g., “did:example:ebfeb1f712ebc6f1c276e12ec21”). The presentation also includes revocationinformation 2F04 (e.g., “id”: “http://example.gov/revocations/738” and“type”: “SimpleRevocationList2017”). The presentation also includesinformation to prevent replay 2F06 (e.g., a cryptographically randomnonce, a create date, etc.). In addition, the presentation includesnotations that indicate modification prevention (e.g., a signature overthe presentation) and communication channel information (e.g., thepresentation can be encrypted with the public key of the targetrecipient, allowing a channel specific authorization and additionalprivacy and security over the message).

FIG. 2G is a flow diagram illustrating a process for credential storingand verifying using a distributed ledger. In some embodiments, theprocess of FIG. 2G is executed by DCIAMS 2A04 of FIG. 2A. In the exampleshown, in 2G00 an indication is received to register a credential. Forexample, the indication is received from an issuer of a credential tostore the credential associated with an issuer identifier in adistributed ledger. In 2G02, it is indicated to store in the distributedledger a DID document associated with a holder identifier. For example,the issuer provides a credential to a user that is stored in a holderdevice that will later be used for identification or verification. Theinformation regarding the credential will be verified as beingassociated with the holder identifier by checking stored information inthe distributed ledger. In 2G03, a dual signature authentication schemeis employed to authorize storing the DID document based at least in parton an individual signature and a ledger writer signature. For example,an item stored on the distributed ledger is signed using a permissionedwriter and this is used to verify that the item as it has arrived at thedistributed ledger is valid. This item is then prepared to be stored bychecking another associated signature with the item and storing the itemwith this signature—for example, a DID document associated with a holdersignature, a DID document associated with a user signature, a schemaassociated with an issuer signature, a credential definition associatedwith an issuer signature (and in some cases also a credential definitionkey), In 2G04, it is indicated to store in the distributed ledger aschema associated with issuer of the credential. For example, thecredential schema associated with the issuer of the credential is storedon the distributed ledger so that during verification a check can beperformed on the schema of the credential. In 2G06, it is indicated tostore in the distributed ledger a credential definition associated withthe schema. For example, the credential definition is stored from anissuer that is associated with the schema information of the issuer sothat during verification a check can be performed on the credentialdefinition associated with the issuer of the credential. In 2G08, it isindicated to store in the distributed ledger a DID document associatedwith the issuer of the credential. For example, an identifier is storedassociated with the issuer of a credential. In 2G10, it is indicated toverify a credential by checking the distributed ledger. For example, theuser desires to use the credential to verify identity or validity of theinformation in the credential. The user can provide a requestor thatwants to have certification that the identity or the information isvalid and is able to query a server to get the information checked usinginformation stored on a distributed ledger. In some cases, the requestto verify triggers a request to a holder device to provide credentialinformation that is then verified by the server using the distributedledger. The server can then respond to the requestor that the credentialis either verified or not verified.

FIG. 2H is a flow diagram illustrating an embodiment of a process forstoring a document on a distributed ledger. In some embodiments, theflow of FIG. 2H is used to implement 2G02, 2G04, 2G06, or 2G08 of FIG.2G. In the example shown, in 2H00 a document is provided to adistributed ledger. For example, a DCIAMS server system provides adistributed ledger system with a document to be stored on thedistributed ledger. In some embodiments, the distributed ledger isimplemented using a blockchain. In 2H02, it is determined whether asignature failure indication has been received. For example, it isdetermined whether a signature check (e.g., a holder signature check, auser signature check, an issuer signature check, credential definitionkey check, etc.) of the document provided to the distributed ledgersystem passed. In some cases, a failure would indicate that the documentis corrupted in transmission, is not from a valid source, is signed withthe incorrect key, or any other appropriate cause of failure. Inresponse to determining that a signature failure indication is received,in 2H04 it is indicated that the distributed ledger has reported asignature issue and control passes to 2H20. In response to determiningthat a signature failure indication has not been received, in 2H06 it isindicated that the document signature check passed. In 2H08, it isdetermined whether a uniqueness failure indication has been received.For example, it is determined whether a uniqueness check of the documentprovided to the distributed ledger system passed. In some cases, afailure would indicate that the document is already stored on thedistributed ledger either in whole or in part, that the documentincludes data that is not able to be stored on the distributed ledger,that the document identifier matches a document identifier of an alreadystored document, or any other appropriate cause of failure. In responseto determining that a uniqueness failure indication is received, in 2H10it is indicated that the distributed ledger has reported a uniquenessissue and control passes to 2H20. In response to determining that auniqueness failure indication has not been received, in 2H12 it isindicated that the document uniqueness check passed. In 2H14, it isdetermined whether a storage failure indication has been received. Forexample, it is determined whether a storage operation for the documentprovided to the distributed ledger system failed. In some cases, afailure would indicate that the blockchain storage system is notworking, the blockchain storage system is not able to store thedocument, local node is out of disk/storage capacity, local node ishaving a hardware failure, or any other appropriate cause of failure. Inresponse to determining that a storage failure indication is received,in 2H16 it is indicated that the distributed ledger has reported astorage issue and control passes to 2H20. In response to determiningthat a storage failure indication has not been received, in 2H18 it isindicated that the document storage was successful, and the processends. In 2H20, it is indicated that document storage failed and theprocess ends.

FIG. 21 is a flow diagram illustrating an embodiment of a process forverifying a credential. In some embodiments, the process of FIG. 21 isused to implement 2G10 of FIG. 2G. In the example shown, in 2100 it isindicated to check the schema. For example, the DCIAMS system indicatesto the distributed ledger system to check the schema associated with acredential. The schema associated with the credential is retrieved fromthe distributed ledger and compared with the credential schema todetermine whether the schema matches. In 2102, it is determined whethera response indicates that the schema matches. For example, thedistributed ledger checks the schema of the credential with thedistributed ledger stored schema. In some embodiments, checking theschema includes checking a signature associated with the schema (e.g.,an issuer signature). In response to determining that the schema doesnot match, in 2104 it is indicated that the distributed ledger reportedthat the schema does not match, and control passes to 2122. In responseto determining that the schema does match, in 2106 it is indicated thatthe schema matches. For example, the distributed ledger has reportedthat the credential schema matches to the credential schema stored onthe distributed ledger. In 2108, it is determined whether a responseindicates that the credential definition matches. For example, thedistributed ledger checks the credential definition of the credentialwith the distributed ledger stored credential definition. In someembodiments, the credential definition is checked using a signaturecheck (e.g., a check of an issuer signature, a check of a credentialdefinition signature, etc.). In response to determining that thecredential definition does not match, in 2110 it is indicated that thedistributed ledger reported that the credential definition does notmatch, and control passes to 2122. In response to determining that thecredential definition does match, in 2112 it is indicated that thecredential definition matches. For example, the distributed ledger hasreported that the credential definition matches to the credentialdefinition stored on the distributed ledger. In 2114, it is determinedwhether a response indicates that the credential is revoked. Forexample, the distributed ledger checks a revocation list to determinewhether the credential has been revoked by the issuer. In response todetermining that the credential was revoked, in 2116 it is indicatedthat the distributed ledger reported that the credential was revoked,and control passes to 2122. In response to determining that thecredential was not revoked, in 2118 it is indicated that the credentialis not revoked, and control passes to 2120. For example, the distributedledger has reported that the credential is not on a revocation list ofthe distributed ledger or associated with the distributed ledger. In2120, it is indicated that the credential is verified, and the processends. For example, it is indicated to the requestor from the DCIAMS thatthe credential is verified by using the distributed ledger. In 2122, itis indicated that the credential is not verified, and the process ends.For example, it is indicated to the requestor from the DCIAMS that thecredential is not verified by using the distributed ledger.

A system for credential storing and verifying using a distributed ledgeris disclosed. The system includes an interface and a processor. Theinterface is configured to receive an indication to register acredential. The processor is configured to indicate to store in adistributed ledger a decentralized identifier (DID) document associatedwith a holder identifier using a smart contract, wherein storing usingthe smart contract employs a dual signature authentication scheme toauthorize storing based at least in part on an individual signature anda ledger writer signature; indicate to store in the distributed ledger aschema associated with an issuer of the credential; and indicate tostore in the distributed ledger a credential definition associated withthe schema. In some embodiments, the DID document associated with theholder identifier comprises a public key and a private key. In someembodiments, storing the DID document associated with the holderidentifier includes checking a signature for the DID document associatedwith the holder identifier. In some embodiments, storing the DIDdocument associated with the holder identifier includes checkinguniqueness for the DID document associated with the holder identifier.In some embodiments, the distributed ledger comprises a blockchain. Insome embodiments, the processor is further configured to store in thedistributed ledger an issuer DID document associated with the issuer ofthe credential. In some embodiments, the credential is provided to aholder device associated with the holder identifier. In someembodiments, the holder device sends a presentation regarding thecredential to a verifier. In some embodiments, the verifier verifies thecredential by indicating to check the distributed ledger. In someembodiments, checking the distributed ledger comprises determiningwhether the schema stored in the distributed ledger associated with thepresentation regarding the credential is matches the credential. In someembodiments, in response to determining the schema stored in thedistributed ledger associated with the presentation regarding thecredential matches the credential, indicate that the credential matches.In some embodiments, in response to determining the schema stored in thedistributed ledger associated with the presentation regarding thecredential does not match the credential, indicate that the credentialdoes not match. In some embodiments, checking the distributed ledgercomprises determining whether the credential definition stored in thedistributed ledger associated with the presentation regarding thecredential is matches the credential. In some embodiments, in responseto determining the schema stored in the distributed ledger associatedwith the presentation regarding the credential matches the credential,indicate that the credential matches. In some embodiments, in responseto determining the schema stored in the distributed ledger associatedwith the presentation regarding the credential does not match thecredential, indicate that the credential does not match. In someembodiments, checking the distributed ledger comprises determiningwhether the credential definition stored in the distributed ledgerassociated with the presentation regarding the credential is matches thecredential. In some embodiments, in response to determining thecredential definition stored in the distributed ledger associated withthe presentation regarding the credential matches the credential,indicate that the credential matches. In some embodiments, in responseto determining the credential definition stored in the distributedledger associated with the presentation regarding the credential doesnot match the credential, indicate that the credential does not match.In some embodiments, checking the distributed ledger comprisesdetermining whether the revocation registry stored in the distributedledger associated with the presentation regarding the credentialindicates the credential is revoked. In some embodiments, in response todetermining the credential is indicated as revoked, indicate that thecredential is revoked. In some embodiments, in response to determiningthe credential is indicated as not revoked, indicate that the credentialis not revoked.

Case C—Digital Credentials for Primary Factor Authentication

A system for credential authentication comprises an interface configuredto receive a request for authorization to access from an application,and a processor configured to determine a set of credentials that canenable authorization to access, generate a proof request challenge,receive a proof response, determine that the proof response is validbased at least in part on information stored in a distributed ledger,generate a token, and provide the token.

A system for credential authentication comprises a server system forauthorizing a login using a credential. A user using a user app (e.g., aweb browser) on a user system requests access to a remote application(e.g., a web accessible application—for example, a databaseapplication). The remote application requests that the system forcredentialing authorize the login attempt. The system for credentialingauthorizes the login attempt by requesting a credential that proves theuser has the qualifications to access the remote application. The useris associated with an authentication device including digitalcredentials and a digital identity application for accessing thecredentials. When the system for credentialing is first requested toauthorize access, it provides a secure code—for example, a quickresponse (QR) code—to the user device. The user then uses theauthentication device to capture the secure code data (e.g., secure codedata that is a time bounded one time use token acquired by imaging theQR code). The digital identity application on the authentication deviceprovides the secure code data and the public key of the user registeringto the system for credentialing creating an association between theregistering user on the application instance and the user record in thecredential authentication system, linking the user using the user appwith the authentication device. Following a successful authenticationattempt, the system for credential authentication provides a securecookie including identifier data for the authentication device to theuser app in order to streamline this process for future login attempts.The system for credential authentication provides a proof requestcomprising a request for one of a set of credentials (e.g., the set ofcredentials that can prove the user is qualified to access the remoteapplication) to the authentication device. The authentication devicedetermines the credentials, if any, it has stored that satisfy the proofrequest and provides the user with a user interface allowing the user toselect the credential desired to use to authorize login. Theauthentication device additionally prompts the user to confirm signing aproof response using a private key. When a credential is selected thatthe user has confirmed signing, the authentication device creates aproof response comprising the credential and signs the proof responseusing a private key. The authentication device provides the signed proofresponse to the credential authentication system. The credentialauthentication system validates the signature and extracts and validatesthe credential. For example, the credential system determines, usinginformation stored in a distributed ledger, whether the credentialsatisfies the proof request, whether the credential is valid and notexpired, whether the credential is not revoked, etc. In the event thecredential system determines that the proof response is satisfactory, itprovides a login token back to the remote application authorizing thelogin. Once the remote application has received the login token, itgrants access to the user. The login token is stored to enable futurelogin attempts. The login token is then used for automatically enablingaccess until the login is token is determined to be expired. In variousembodiments, the login token expires after a predetermined time, after apredetermined number of logins, or under any other appropriateconditions.

FIG. 3A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 3A comprises anetwork system for a database processing system. In the example shown,FIG. 3A comprises network 3A00. In various embodiments, network 3A00comprises one or more of the following: a local area network, a widearea network, a wired network, a wireless network, the Internet, anintranet, a storage area network, or any other appropriate communicationnetwork. Authentication device 3A02, distributed ledger 3A04, digitalcredential aware identity and access management service (DCIAMS) 3A06,database system 3A08, and user system communicate via network 3A00.Authentication device 3A02 comprises an authentication device associatedwith a user (e.g., a user of database system 3A08, a user using usersystem 3A10). For example, authentication device 3A02 comprises acomputer, a smartphone, a tablet, a mobile device, etc. Distributedledger 3A04 comprises a distributed ledger (e.g., a decentralizedledger, a public ledger, a permissioned ledger, a blockchain, etc.). Forexample, distributed ledger 3A04 is stored on a plurality of systems andcomprises one or more permissioned writer systems for writing to thedistributed ledger. DCIAMS 3A06 comprises a system for interacting withauthentication device 3A02, distributed ledger 3A04, database system3A08, and any other appropriate systems. DCIAMS 3A06 comprises a systemfor coordinating a login for database system 3A08, for providing acredential to authentication device 3A02, for requesting a credentialfrom authentication device 3A02, for verifying a user identifier or asignature in distributed ledger 3A04, etc. Database system 3A08comprises a system for storing database data, requesting database data,creating a report based on database data, creating a document, accessinga document, to executing a database application, etc. A user uses usersystem 3A10 to access data stored on database system 3A08. For example,a user uses an application on user system 3A10 (e.g., a web browser) toconnect to an application on database system 3A08 (e.g., a databaseapplication). The application on database system authenticates a userlogin before granting access.

DCIAMS 3A06 comprises a system for using a digital credential toauthenticate a login (e.g., a user login to a database system). Forexample, DCIAMS 3A06 an interface configured to receive a request froman application for authorization to access, and a processor configuredto determine a set of credentials that can enable authorization toaccess, generate a proof request challenge, receive a proof response,determine that the proof response is valid using a distributed ledger,generate a token, and provide the token.

In some embodiments, DCIAMS 3A06 helps to protect application systemsother than database systems.

FIG. 3B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 3B00of FIG. 3B comprises authentication device 3A02 of FIG. 3A. In theexample shown, authentication device 3B00 comprises interface 3B02. Forexample, interface 3B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 3B04comprises a processor for executing applications 3B06. Applications 3B06comprise digital identity application 3B08 and any other appropriateapplications. Digital identity application 3B08 comprises an applicationfor providing a proof response in response to a proof request. Forexample, digital identity application 3B08 comprises an application forreceiving a proof request challenge from a DCIAMS (e.g., DCIAMS 3A06 ofFIG. 3A), determining one or more credentials that match the request,providing a credential list to a user for credential selection, in theevent it is determined that a credential is selected, creating a proofresponse, providing a request to sign the proof response, and in theevent permission to sign the proof response is received, unlocking amobile encryption key, decrypting an identity key pair private key usingthe mobile encryption key, signing the proof response using the identitykey pair private key, and providing the signed proof response. Secureenclave 3B10 comprises a secure system for storing a mobile encryptionkey. Secure enclave 3B10 comprises mobile encryption key 3B12 andencryption decryption application 3B14. For example, secure enclave 3B10comprises multiple mobile encryption keys, an application for generatingand/or removing mobile encryption keys, etc. Secure enclave 3B10comprises a system for receiving data, transforming it by encryptingand/or decrypting the data using a mobile encryption key or keys, andproviding the transformed data. For example, secure enclave 3B10 isconfigured to only provide transformed input data and not to providemobile encryption key 3B12. In some embodiments, functionality of secureenclave 3B10 is access limited using a biometric (e.g., a fingerprint, aretina scan, a DNA scan, etc.) or a personal identification number(PIN). Authentication device 3B00 additionally comprises storage 3B16.Storage 3B16 comprises encryption keys 3B18—for example comprising apublic key of an identity key pair, a private key of an identity keypair, a private key of an identity key pair encrypted using mobileencryption key 3B12, etc. Storage 3B16 additionally comprises digitalcredentials 3B20, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.Authentication device 3B00 additionally comprises memory 3B22. Memory3B22 comprises executing application data 3B24, comprising dataassociated with applications 3B06.

FIG. 3C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 3C00 comprises DCIAMS 3A06 of FIG. 3A. In theexample shown, DCIAMS 3C00 comprises interface 3C02. For example,interface 3C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. Processor 3C04 comprises aprocessor for executing applications 3C06. Applications 3C06 comprises aset of DCIAMS applications. Decryption application C308 comprises anapplication for decrypting encrypted data using a key. Login application3C10 comprises an application for receiving login information (e.g.,username and password, a credential, a QR code challenge, etc.) andproviding login credentials (e.g., a login token). Ledger interfaceapplication 3C12 comprises an application for interacting with adistributed ledger (e.g., distributed ledger 3A04 of FIG. 3A). Forexample, ledger interface application 3C12 comprises an application forverifying a signature in a ledger or checking a credential identifierfor revocation in a ledger. Proof request application 3C14 comprises anapplication for creating a proof request, sending a proof request,evaluating a proof request response (e.g., a proof response), etc. Tokengeneration application 3C16 comprises an application for generating alogin token (e.g., in response to a successful login). Credentialissuing application 3C18 comprises an application for issuing a digitalcredential for proving a qualification in response to a request from acredential issuing authority to issue the credential. Applications 3C06additionally comprise any other appropriate applications. For example,processor 3C04 comprises a processor configured to receive a request forauthorization to access from an application, determine a set ofcredentials that can enable authorization to access, generate a proofrequest challenge, receive a proof response, determine that the proofresponse is valid, generate a token, and provide the token. Storage 3C20comprises user and device database 3C22 and credential rules 3C24. Userand device database 3C22 comprises a database of registered users for agiven customer organization and user details (e.g., username, passwordhash, contact information, email address, relationship to devices,registered public keys, registered mapping documents in a distributedledger, etc.). User and device database 3C22 additionally comprises adevice directory comprising all the devices for a given customerorganization as well as mapping documents associated with the devicesand relationships with users associated with the devices. Credentialrules 3C24 comprises a set of credential rules for determining acredential that satisfies a given access request—for example, rulesrelated to a credential associated schema, a credential associatedorganization, a credential issuer, a credential associated location, acredential associated class identifier, a credential associated licensenumber, or any other appropriate credential rules. In variousembodiments, rules comprise rules related to a credential associatedschema, rules related to a credential associated organization, rulesrelated to a credential issuer, rules related to a credential associatedlocation, rules related to a credential associated class identifier oridentifier number, rules related to a credential associated license orlicense number, a credential associated class name, or any otherappropriate credential rules. In some embodiments, the rules are appliedselectively (e.g., based at least in part on a user identifier)—forexample, employees with a credential can access application A,contractors with a credential can access application B, or any otherappropriate matching of access with identifiers. In various embodiments,the rules are applied selectively based at least in part on currentemployment, employee type, location of user, qualification by trainingclass, credential from a third party issuer (e.g., division of motorvehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked). DCIAMS 3C00 additionallycomprises memory 3C26. Memory 3C26 comprises executing application data3C28, comprising data associated with applications 3C06.

FIG. 3D is a flow diagram illustrating an embodiment of a process forauthenticating a login. In some embodiments, the process of FIG. 3D isexecuted by database system (e.g., database system 3A08 of FIG. 3A) forauthenticating a login attempt from user system (e.g., user system 3A10of FIG. 3A). In the example shown, in 3D00, an attempt is received toaccess an application via an external system. In 3D02, it is determinedwhether a login token is present. For example, the token authorizesaccess to the application for a user. In the event it is determined thata login token is present (e.g., as a result of a previous successfullogin), control passes to 3D04. In 3D04, access is provided, and theprocess ends. In the event it is determined in 3D02 that a login tokenis not present, control passes to 3D06. In 3D06, a request forauthorization to access is provided. For example, an application system(e.g., a database system) provides a request for authorization to accessthe application system to a DCIAMS. In 3D08, it is determined whetherthe DCIAMS authorizes access. In the event it is determined that theDCIAMS does not authorize access (e.g., that the access attempt timesout, that an indication is received indicating that the access is notauthorized, etc.), the process ends. In the event it is determined in3D08 that the DCIAMS authorizes access, control passes to 3D10. In 3D10,a login token is received from the DCIAMS. For example, the login tokenis stored (e.g., to authorize access to the application in a futurelogin attempt). In 3D12, access is provided.

FIG. 3E is a flow diagram illustrating an embodiment of a process forcredential based app authorization . In some embodiments, the process ofFIG. 3E is executed by a DCIAMS (e.g., DCIAMS 3A06 of FIG. 3A) inresponse to access attempt redirect (e.g., access attempt redirect 3D06of FIG. 3D). In the example shown, in 3E00, a request for authorizationto access is received from an application. In 3E02, a set of credentialsthat can enable authorization to access is determined. For example,specific credentials are placed in the set of credentials in the eventthat the specific credential satisfies the rules necessary to grantaccess. In various embodiments, rules comprise rules related to acredential associated schema, rules related to a credential associatedorganization, rules related to a credential issuer, rules related to acredential associated location, rules related to a credential associatedclass identifier or identifier number, rules related to a credentialassociated license or license number, a credential associated classname, or any other appropriate credential rules. In some embodiments,the rules are applied selectively (e.g., based at least in part on auser identifier)—for example, employees with a credential can accessapplication A, contractors with a credential can access application B,or any other appropriate matching of access with identifiers. In variousembodiments, the rules are applied selectively based at least in part oncurrent employment, employee type, location of user, qualification bytraining class, credential from a third party issuer (e.g., division ofmotor vehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked).

In 3E04, a proof request challenge is generated. For example, the proofrequest challenge comprises a request for a credential of the set ofcredentials that can enable authorization to access. In someembodiments, generating the proof request challenge is based upon aconfigured set of proof request challenge rules, wherein the configuredset of proof request challenge rules comprise one or more criteria whichdetermine the set of credentials that can enable authorization toaccess. In some embodiments, the rule(s) comprise rule(s) that need tobe satisfied to grant access similar to the rules above for the specificcredential. In 3E06, it is determined whether the request forauthorization to access includes a secure cookie. For example, thesecure cookie comprises a secure cookie stored during a previousexecution. In the event it is determined that the request forauthorization to access does not include a secure cookie, control passesto 3E10. In 3E10, a uniform record identifier (URI) is determined usinga quick response (QR) code process. Control then passes to 3E12. In theevent it is determined in 3E06 that the request for authorization toaccess includes a secure cookie, control passes to 3E08. In 3E08, auniform record identifier (URI) is received based at least in part onthe secure cookie. For example, the secure cookie maps in the DCIAMS toa device id that is running the digital identity app. The DCIAMS is thenable to push the URI to the digital identity app. Control then passes to3E12. In 3E12, the proof request challenge is provided to a digitalidentity app using the URI. For example, the URI is used by the digitalidentity app to pull down the data associated with that proof requestchallenge from a server. The URI allows the push message or the QRencoded message to remain small and/or reasonable regardless of thecontent or size of the proof request challenge. In 3E14, a proofresponse is received. In 3E16, it is determined whether the proofresponse is valid. For example, the proof response is checked againstinformation that is stored/registered in a distributed ledger (e.g., apermissioned ledger, a decentralized ledger, a public ledger, ablockchain, etc.). In the event it is determined that the proof responseis not valid, the process ends. In the event it is determined that theproof response is valid, control passes to 3E18. In 3E18, a login tokenis generated. In 3E20, the login token is provided to the requestingapplication. In 3E22, a secure cookie is provided to a user application(e.g., a user application on a user system). For example, the securecookie is provided to the user application via the requestingapplication.

FIG. 3F is a flow diagram illustrating an embodiment of a process fordetermining a uniform record identifier using a QR code process. In someembodiments, the process of FIG. 3F implements 3E10 of FIG. 3E. In theexample shown, in 3F00, an authorization QR code is received at theapplication. In 3F02, the authorization QR code data is validated. In3F04, a URI is determined from the authorization QR code.

FIG. 3G is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 3G implements 3E16 of FIG. 3E. In the example shown, in3G00, a DID document is retrieved from a distributed ledger based ontarget DID in proof response. In 3G02, it is determined whether a publickey from a distributed ledger matches a DID (e.g., a decentralizedidentifier) in a credential (e.g., a credential of the proof response).In the event it is determined that a public key from a distributedledger does not match a DID in the credential, control passes to 3G14.In the event it is determined in 3G02 that the public key from thedistributed ledger matches the DID in the credential, control passes to3G04. In 3G04, it is determined whether the credential is one of a setof credentials that can enable authorization to access. In the event itis determined that the credential is not one of the set of credentialsthat can enable authorization to access, control passes to 3G14. In theevent it is determined in 3G04 that the credential is one of the set ofcredentials that can enable authorization to access, control passes to3G06. In 3G06, it is determined whether the credential is expired. Inthe event it is determined that the credential is expired, controlpasses to 3G14. In the event it is determined in 3G06 that thecredential is not expired, control passes to 3G08. In 3G08, it isdetermined whether the credential signature is valid. For example,determining whether the credential signature is valid uses the publickey from the DID document on the ledger. In the event it is determinedthat the credential signature is not valid, control passes to 3G14. Inthe event it is determined in 3G08 that the credential signature isvalid, control passes to 3G10. In 3G10, it is determined whether thecredential is revoked. For example, determining that the credential isrevoked comprises querying a revocation registry of a revocationdatabase or a distributed ledger (e.g., a decentralized ledger, apermissioned ledger, a public ledger, a blockchain, etc.)In the eventthat the credential is revoked, control passes to 3G14. In the event thathe credential is not revoked, control passes to 3G12. In 3G12, theprocess indicates that the proof response is valid, and the processends. In 3G14, the process indicates that the proof response is notvalid, and the process ends. .

FIG. 3H is a flow diagram illustrating an embodiment of a process for adigital identity application. In some embodiments, the process of FIG.3H is executed by authentication device 3A02 of FIG. 3A. In the exampleshown, in 3H02, a proof request challenge is fetched from the DCIAMSusing URI. For example, the URI received via a push or via a QR is usedto fetch a proof request challenge, In some embodiments, the proofrequest challenge is fetched from a server which is not the DCIAMS. In3H04, one or more credentials that match the request are determined. In3H06, a credential list is provided to a user for credential selection.In 3H08, it is determined whether a credential is selected. In the eventit is determined that a credential is not selected, the process ends. Inthe event it is determined that a credential is selected, control passesto 3H10. In 3H10, a proof response (e.g., comprising the selected one ormore credentials) is created. In 3H12, a request is provided forpermission to sign the proof response. In 3H14, it is determined whetherpermission is received to sign the proof response. In the event it isdetermined that permission to sign the proof response is not received,the process ends. In the event it is determined in 3H14 that permissionto sign the proof response is received, control passes to 3H16. In 3H16,a mobile encryption key is unlocked. In some embodiments, unlocking themobile encryption key requires an additional authorization—for example,the unlocking requires a biometric data or a PIN be entered by a user.In 3H18, an identity key pair private key is decrypted using the mobileencryption key. In 3H20, the proof response is signed using the identitykey pair private key. In 3H22, the signed proof response is provided. Insome embodiments, the signed proof response is encrypted using a perchannel key.

A system for credential authentication includes and interface and aprocessor. The interface is configured to receive a request forauthorization to access from an application. The processor is configuredto determine a set of credentials that can enable authorization toaccess; generate a proof request challenge; receive a proof response;determine that the proof response is valid based at least in part oninformation stored in a distributed ledger; generate a token; andprovide the token. In some embodiments, generating the proof requestchallenge is based upon a configured set of proof request challengerules, wherein the configured set of proof request challenge rulescomprises one or more criteria which determine the set of credentialsthat can enable authorization to access. In some embodiments, the proofrequest challenge is provided to a digital identity app. In someembodiments, the proof request challenge is provided to the digitalidentity app using a URI that points to the proof request challenge. Insome embodiments, the digital identity app is on a mobile device. Insome embodiments, the proof request challenge is provided to the mobiledevice using a push notification. In some embodiments, the mobile deviceis identified for the push notification using a secure cookie storedduring a previous execution. In some embodiments, the proof requestchallenge is provided to the mobile device using a QR code, whichcomprises a URI that points to the proof request challenge. In someembodiments, the QR code is scanned by the mobile device to access theproof request challenge. In some embodiments, the proof responseincludes a credential. In some embodiments, the credential comprises auser selected credential. In some embodiments, the proof response issigned using a private key of an identity key pair. In some embodiments,the private key is decrypted using a mobile encryption key. In someembodiments, the mobile encryption key is accessed using a biometric. Insome embodiments, the proof response is encrypted using a per channelkey. In some embodiments, determining that the proof response is validcomprises determining that the proof response comprises one or morecredentials of a set of credentials, wherein the set of credentialscomprises credentials satisfying rules for granting access. In someembodiments, determining that the proof response is valid comprises oneor more of: determining that a credential of the proof response is notexpired, determining that the credential of the proof response includesa valid signature, and/or determining that a credential decentralizedidentifier matches a key holder associated with request. In someembodiments, determining that the proof response is valid comprisesdetermining that a credential of the proof response is not revoked. Insome embodiments, determining that the credential of the proof responseis not revoked comprises querying a revocation registry of a distributedledger. In some embodiments, the token authorizes access to theapplication for a user. In some embodiments, the token is stored by theapplication. In some embodiments, the processor is further configured toprovide a secure cookie for device identification during a futureexecution.

Case D—Digital Credentials for User Device Authentication

A system for credential authentication comprises an interface configuredto receive a request from an application for authorization to access,wherein access to the application is requested by a user using a userdevice, and a processor configured to provide an authentication requestto the user device, receive a device credential, wherein the devicecredential is backed by data stored in a distributed ledger, determine auser identifier and an authentication device associated with the userbased at least in part on the device credential, provide a proof requestto the authentication device, receive a proof response, determine thatthe proof response is valid, generate a token, and provide the token tothe application authorizing access for the user.

A system for digital credentials for user device authenticationcomprises a system for credentialing in communication with anapplication system, a user system, and an authentication device. A useruses the user system to access an application on the application system.For example, the user uses a web browser on the user system to access anapplication on the application system. The authentication systemcomprises a system (e.g., a mobile system, a mobile device, asmartphone, etc.) for storing authentication information (e.g., digitalcredentials, encryption keys, etc.) for the user. When the user attemptsto access an application on the application system, the applicationsystem requests authorization to access from the system for digitalcredentials. The system for digital credentials provides a request tothe user system for a user device authentication. In the event the userdevice has not authenticated recently, the user system responds to therequest for user device authentication with a device credential. Thedevice credential comprises a secure indication of the user deviceidentity. The system for digital credentials determines the requestinguser based on the device, and determines an authentication device basedon the user. The system for digital credentials additionally determinesa set of credentials that can be used to authenticate access to theapplication, creates a proof request including an indication of the setof credentials, and provides the proof request to the authenticationsystem. The authentication system provides the user with an indicationto use a credential to satisfy the proof request and to sign the proofresponse using an encryption key. In response to a user confirmation theauthentication system creates and signs the proof response, and providesthe proof response to the system for digital credentials. The system fordigital credentials verifies the proof response using the distributedledger and generates a lease key for granting access to the user devicefor a predetermined time period, as well as an authentication token, andprovides the lease private key and the authentication token to the userdevice. The lease key is encrypted using the public key of theauthentication device, requiring the user device to access theauthentication device in order to utilize it. The authentication tokenis signed with the lease key allowing it to be used immediately. Theuser device provides the signed authentication token back as proof ofauthentication, and the system for digital credentials provides a logintoken to the application system to verify login.

Upon a second user device request to access an application on theapplication system during the lifetime of the lease key, the system fordigital credentials provides a second request to the user system for auser device authentication. The user system determines that a validlease key is present. In order to utilize the lease key the user systemsigns the encrypted lease key with the user system private key andprovides the signed encrypted lease key to the authentication device. Insome embodiments, in addition to signing the encrypted lease key, onemore outer encryption layer(s) (e.g., a hybrid cryptographic system, aNacl box encryption system, etc.) is/are used to protect the valueduring transmission from being copied or stolen. using a hybrid cryptosystem like Nacl box encryption so that the signed token value cannot becopied, stolen over the wire. Communication between the user device andthe authentication system is performed using a proximity radiosystem—for example, a Bluetooth system. The authentication device checksthe signature and decrypts the lease key. It then creates a newauthentication token signed with the lease key, encrypts theauthentication token with the user device public key, and provides theencrypted token back to the user device. The user device decrypts thetoken and provides the token to the system for digital credentials. Inresponse to the token, the system for digital credentials provides alogin token to the application system to verify login. Authenticatingthe second device request during the lifetime of the lease key thusrequires proximity of the authentication system to the user system butdoes not require the user to provide a credential a second time.

In some embodiments, the system for credential authentication comprisesa split key security model—for example, the authentication device (e.g.,a user's phone) doesn't hold the encrypted session key, the user device(e.g., a user's laptop) doesn't have the key to unlock the session key,and proximity is the only thing allowing them to work together to answerchallenges. In order to answer a challenge, the authentication deviceneeds to be sitting near to the user device—for example, if the laptopis able to ping the phone, the laptop should maintain its permission toaccess the system; if the laptop is not able to ping the phone, thesystem can inform the user that the laptop is not able to respond to thechallenges without the phone's decryption help. In this example, thesecurity virtue is that a session key sits on the laptop, encrypted witha key that the laptop does not have. When a request challenge comes inthat needs signing, the laptop messages the authentication device (i.e.,a user's phone), which unlocks the session key, signs the requestchallenge, and then sends the signed challenge response back. For thissystem, the decrypted session private key never has to be stored on thelaptop, and control is needed both of the user device with the encryptedkey and the authentication device to successfully obtain authorizationto gain access, but only having one of the two will not let you in.

The credential authentication system makes a computer system better byimproving security and access control. The configuration of havingmutually reliant components keeps the system more secure and preventsopportunistic access of the system by requiring proximity of twocomponents (e.g., a user device and an authentication device).

FIG. 4A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 4A comprises anetwork system for a credential system. In the example shown, FIG. 4Acomprises network 4A00. In various embodiments, network 4A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 4A02, distributed ledger 4A04, digital credentialaware identity and access management service 4A06, application system4A08, and user system communicate via network 4A00. Authenticationdevice 4A02 comprises an authentication device associated with a user(e.g., a user of application system 4A08, a user using user system4A10). For example, authentication device 4A02 comprises a computer, asmartphone, a tablet, a mobile device, etc. Distributed ledger 4A04comprises a distributed ledger (e.g., a decentralized ledger, a publicledger, a permissioned ledger, a blockchain, etc.). For example,distributed ledger 4A04 is stored on a plurality of systems andcomprises one or more permissioned writer systems for writing to thedistributed ledger. Digital credential aware identity and accessmanagement service (DCIAMS) 4A06 comprises a system for interacting withauthentication device 4A02, distributed ledger 4A04, application system4A08, and any other appropriate systems. DCIAMS 4A06 comprises a systemfor coordinating a login for application system 4A08, for providing acredential to authentication device 4A02, for requesting a credentialfrom authentication device 4A02, for verifying a user identifier or asignature in distributed ledger 4A04, etc. Application system 4A08comprises a system for providing access to an application. For example,application system 4A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system4A10 to access applications on application system 4A08. For example, auser uses an application on user system 4A10 (e.g., a web browser) toconnect to an application on application system 4A08. The application onapplication system 4A08 authenticates a user login before grantingaccess.

DCIAMS 4A06 comprises a system for using a digital credential toauthenticate a login (e.g., a user login to an application system). Forexample, DCIAMS 4A06 comprises an interface configured to receive arequest from an application for authorization to access, wherein accessto the application is requested by a user using a user device, and aprocessor configured to provide an authentication request to the userdevice, receive a device credential, determine a user identifier and anauthentication device associated with the user based at least in part onthe device credential, provide a proof request to the authenticationdevice, receive a proof response, determine that the proof response isvalid, generate a token, and provide the token to the applicationauthorizing access for the user.

FIG. 4B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 4B00of FIG. 4B comprises authentication device 4A02 of FIG. 4A. In theexample shown, authentication device 4B00 comprises interface 4B02. Forexample, interface 4B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Interface 4B02comprises proximity radio system 4B04. Proximity radio system 4B04comprises a radio system for communication over a short distance. Forexample, proximity radio system 4B04 comprises a Bluetooth system, aZigbee system, an ultrawideband system, a near field communication (NFC)system, an infrared communications system, a wireless personal areanetwork system, etc. Processor 4B06 comprises a processor for executingapplications 4B08. Applications 4B08 comprise digital identityapplication 4B10 and any other appropriate applications. Digitalidentity application 4B10 comprises an application for providing a proofresponse in response to a proof request. For example, digital identityapplication 4B10 comprises an application for receiving a proof requestchallenge from a DCIAMS (e.g., DCIAMS 4A06 of FIG. 4A), determining oneor more credentials that match the request, providing a credential listto a user for credential selection, in the event it is determined that acredential is selected, creating a proof response, providing a requestto sign the proof response, and in the event permission to sign theproof response is received, unlocking a mobile encryption key,decrypting an identity key pair private key using the mobile encryptionkey, signing the proof response using the identity key pair private key,and providing the signed proof response. Digital identity application4B10 additionally comprises an application for receiving (e.g., viaproximity radio system 4B04) a request comprising an authenticationtoken and a lease key encrypted with an authentication device public keyand signed with a user device private key, determining whether the userdevice signature is valid, and in response to a determination that theuser device signature is valid, decrypting the lease key and theauthentication token, signing the authentication token with the leasekey, encrypting the signed authentication token with the user devicepublic key, and providing (e.g., via proximity radio system 4B04) theencrypted signed authentication token to the user device. For example,prior to utilizing digital identity application 4B10, authenticationdevice 4B00 requires the user to login.

Secure enclave 4B12 comprises a secure system for storing a mobileencryption key. Secure enclave 4B12 comprises mobile encryption key 4B14and encryption decryption application 4B16. For example, secure enclave4B12 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave4B12 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave4B12 is configured to only provide transformed input data and not toprovide mobile encryption key 4B14. In some embodiments, functionalityof secure enclave 4B12 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) or a personalidentification number (PIN). Authentication device 4B00 additionallycomprises storage 4B18. Storage 4B18 comprises encryption keys 4B20—forexample, comprising a public key of an identity key pair, a private keyof an identity key pair, a private key of an identity key pair encryptedusing mobile encryption key 4B14, etc. For example, an identity key pairof authentication device 4B00 comprises a public key used by othersystems for encrypting data in such a way that it can only by decryptedby authentication device 4B00, and a private key for decrypting dataencrypted using the public key or for signing data for proving it camefrom authentication device 4B00. Storage 4B18 additionally comprisesdigital credentials 4B22, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.). Forexample, digital credentials 4B22 comprises a credential wallet. In someembodiments, digital credentials 4B22 comprises a locked digital walletable to be unlocked by a user. For example, digital credentials 4B22 areunlocked using a biometric or a PIN. Once the locked digital wallet isunlocked, a credential is retrieved. Authentication device 4B00additionally comprises memory 4B24. Memory 4B24 comprises executingapplication data 4B26, comprising data associated with applications4B08.

FIG. 4C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service. In someembodiments, digital credential aware identity and access managementservice (DCIAMS) 4C00 comprises DCIAMS 4A06 of FIG. 4A. In the exampleshown DCIAMS 4C00 comprises interface 4C02. For example, interface 4C02comprises an interface for receiving data, providing data, receiving arequest for data, receive a request from an application forauthorization to access, etc. Processor 4C04 comprises a processor forexecuting applications 4C06. Applications 4C06 comprises a set of DCIAMSapplications. Decryption application 4C08 comprises an application fordecrypting encrypted data using a key. Login application 4C10 comprisesan application for receiving login information (e.g., username andpassword, a credential, a quick response (QR) code challenge, etc.) andproviding login credentials (e.g., a login token). Ledger interfaceapplication 4C12 comprises an application for interacting with adistributed ledger (e.g., distributed ledger 4A04 of FIG. 4A). Forexample ledger interface application 4C12 comprises an application forverifying a signature in a ledger or checking a credential identifierfor revocation in a ledger. Proof request application 4C14 comprises anapplication for creating a proof request, sending a proof request,evaluating a proof request response (e.g., a proof response), etc. Tokengeneration application 4C16 comprises an application for generating alogin token (e.g., in response to a successful login). Credentialissuing application 4C18 comprises an application for issuing a digitalcredential for proving a qualification in response to a request from acredential issuing authority to issue the credential. Applications 4C06additionally comprise any other appropriate applications. For example,processor 4C04 comprises a processor configured to provide anauthentication request to the user device, receive a device credential,determine a user identifier and an authentication device associated withthe user based at least in part on the device credential, provide aproof request to the authentication device, receive a proof response,determine that the proof response is valid using a distributed ledger,generate a token, and provide the token to the application authorizingaccess for the user. Storage 4C20 comprises user and device database4C22 and credential rules 4C24. User and device database 4C22 comprisesa database of registered users for a given customer organization anduser details (e.g., username, password hash, contact information, emailaddress, relationship to devices, registered public keys, registeredmapping documents in a decentralized ledger, etc.). User and devicedatabase 4C22 additionally comprises a device directory comprising allthe devices for a given customer organization as well as mappingdocuments associated with the devices and relationships with usersassociated with the devices. Credential rules 4C24 comprises a set ofcredential rules for determining a credential that satisfies a givenaccess request, for example rules related to a credential associatedschema, a credential associated organization, a credential issuer, acredential associated location, a credential associated classidentifier, a credential associated license number, or any otherappropriate credential rules. In various embodiments, rules compriserules related to a credential associated schema, rules related to acredential associated organization, rules related to a credentialissuer, rules related to a credential associated location, rules relatedto a credential associated class identifier or identifier number, rulesrelated to a credential associated license or license number, acredential associated class name, or any other appropriate credentialrules. In some embodiments, the rules are applied selectively (e.g.,based at least in part on a user identifier)—for example, employees witha credential can access application A, contractors with a credential canaccess application B, or any other appropriate matching of access withidentifiers. In various embodiments, the rules are applied selectivelybased at least in part on current employment, employee type, location ofuser, qualification by training class, credential from a third partyissuer (e.g., division of motor vehicle license, certification fromschool, etc.), or any other appropriate criterion. As examples ofconfigurable credential rules to grant access: 1) access is granted inthe event that a credential indicates that the holder is a currentemployee (e.g., issuing company is valid, employee status is notexpired, and not revoked); 2) access is granted in the event that acredential indicates that the holder is an employee in an organizationof the company (e.g., issuing company is valid, organization isspecified organization, employee status is not expired, and notrevoked); 3) access is granted in the event that a credential indicatesthat the holder is an employee in a specified location (e.g., issuingcompany is valid, location is a specified location, employee status isnot expired, and not revoked); 4) access is granted in the event that acredential indicates that the holder has necessary training (e.g.,issuing company is valid, training status is complete, employee statusis not expired, and not revoked); and 5) access is granted in the eventthat a credential indicates that the holder has outside credential(e.g., issuing company is valid, outside credential is valid, outsidecredential issuer is third party, employee status is not expired, andnot revoked). DCIAMS 4C00 additionally comprises memory 4C26. Memory4C26 comprises executing application data 4C24, comprising dataassociated with applications 4C06.

FIG. 4D is a block diagram illustrating an embodiment of a user system.In some embodiments, user system 4D00 of FIG. 4D comprises user system4A10 of FIG. 4A. In the example shown, user system 4D00 comprisesinterface 4D02. For example, interface 4D02 comprises an interface forreceiving data, providing data, receiving a request for data, etc.Interface 4D02 comprises proximity radio system 4D04. Proximity radiosystem 4D04 comprises a radio system for communication over a shortdistance. For example, proximity radio system 4D04 comprises a Bluetoothsystem, a Zigbee system, an ultrawideband system, an infraredcommunications system, a near field communication (e.g., NFC) system, awireless personal area network system, etc. Processor 4D06 comprises aprocessor for executing applications 4D08. Applications 4D08 compriseweb browser application 4D10, user authentication application 4D12, andany other appropriate applications. Web browser application 4D10comprises a web browser application for accessing remote systems via aweb protocol. User authentication application 4D12 comprises anapplication for executing a user authentication process. For example,user authentication application 4D12 comprises an application forreceiving a request to access a network application, providing a requestto the application server to access the application, receiving anauthentication request from a DCIAMS, determining whether a session keyis present (e.g., in encryption keys 4D16), in the event a session keyis stored signing in using a proximity authentication device (e.g., anauthentication device in communication using proximity radio system4D04), in the event a session key is not stored providing a proofresponse comprising a user device credential, receiving anauthentication response including an encrypted session key and anauthentication token, encrypted with a user system public key,decrypting the authentication response, storing the encrypted sessionkey, and providing the authentication token to the DCIAMS. In someembodiments, user authentication application 4D12 comprises a specialform of application that is a kernel level driver able to intercept andact as a universal second factor (U2F) device. In some embodiments, thekernel level driver is able to perform some input-output levelinteraction beyond what a normal application would be able to. In someembodiments, the kernel level driver is a privileged process.

User system 4D00 additionally comprises storage 4D14. Storage 4D14comprises encryption keys 4D16, for example comprising a public key ofan identity key pair, a private key of an identity key pair, a sessionkey, etc. For example, an identity key pair of user system 4D00comprises a public key used by other systems for encrypting data in sucha way that it can only by decrypted by user system 4D00, and a privatekey for decrypting data encrypted using the public key or for signingdata for proving it came from user system 4D00. Storage 4D14additionally comprises digital credentials 4D18, comprising digitalcertificates representing qualifications (e.g., a college degree, workexperience, time living at an apartment, time enrolled in a healthinsurance plan, etc. User system 4D00 additionally comprises memory4D20. Memory 4D20 comprises executing application data 4D22, comprisingdata associated with applications 4D08.

FIG. 4E is a flow diagram illustrating an embodiment of a process foraccessing a network application. In some embodiments, the process ofFIG. 4E is executed by user device 4D00 of FIG. 4D. In the exampleshown, in 4E00, a request is received to access a network application.In 4E02, a request is provided to the application server to access theapplication. In 4E04, an authentication request is received from aDCIAMS. For example, the authentication request comprises a universalsecond factor (e.g., U2F) authentication request. In 4E06, it isdetermined whether there is a session key present (e.g., stored on theuser system). In the event it is determined that a session key ispresent, control passes to 4E08. In 4E08, the system signs in using aproximity authentication device challenge, and the process ends. In theevent it is determined in 4E06 that a session key is not present,control passes to 4E10. In 4E10, a proof response is provided comprisinga user device credential. For example, a user device credential that isbacked by data stored in a distributed ledger is provided as the proofresponse. In various embodiments, the distributed ledger comprises oneor more of the following: a permissioned ledger, a decentralized ledger,a public ledger, a blockchain, or any other appropriate ledger. In 4E12,an authentication response is received including an encrypted sessionkey and an authentication token, encrypted with a user system publickey. In 4E14, the authentication response is decrypted. In 4E16, theencrypted session key is stored. In 4E18, the authentication token isprovided to the DCIAMS. In 4E20, an indication of access to the networkapplication is received.

FIG. 4F is a flow diagram illustrating an embodiment of a process forsigning in using a proximity authentication device challenge. In someembodiments, the process of FIG. 4F implements 4E08 of FIG. 4E. In theexample shown, in 4F00, a request is provided comprising an encryptedsession key and authentication token to an authentication device via aproximity radio system. For example, the authentication token comprisesa raw challenge that the DCIAMS sent via U2F to the browser on the userdevice and is being provided to the authentication device so it can besigned. In 4F02, the decrypted authentication token is received signedwith the session key and encrypted with the user device public key viathe proximity radio system. For example, the authentication devicedecrypts the session key, signs the challenge, and encrypts thechallenge to send back to the user device. In 4F04, the authenticationtoken is decrypted. In 4F06, it is determined whether the device keysignature is valid. For example, the In the event it is determined thatthe device key signature is not valid, the process ends. In the event itis determined that the device key signature is valid, control passes to4F08. In 4F08, the authentication token is provided to the DCIAMS. Forexample, the user device then replies via the U2F protocol to theDCIAMS, which determines that the challenge is signed correctly andmatches the session key and then indicates to the application thataccess is authorized.

FIG. 4G is a flow diagram illustrating an embodiment of a process forcredential based authorization. In some embodiments, the process of FIG.4G is executed by DCIAMS 4C00 of FIG. 4C. In the example shown, in 4G00,a request is received from an application for authorization to access,wherein access to the application is requested by a user using a userdevice. In 4G02, an authentication request is provided to the userdevice. For example, the authentication request comprises a universalsecond factor (e.g., U2F) authentication request. In some embodiments,the U2F authentication request comprises a presigned token from theDCIAMS. In 4G04, an authentication response comprising a devicecredential is received. For example, the authentication response fromthe user device is received and checked to make sure that the responseis valid, wherein validating the authentication response compriseschecking a device signature of the authentication response. In 4G06, auser identifier and an authentication device associated with the userare determined based at least in part on the device credential. In 4G08,a proof request is provided to the authentication device. For example,the DCIAMS creates the proof request. In some embodiments, the proofrequest comprises a request for one or more credentials of a set ofcredentials (e.g., a set of credentials that can enable authorization toaccess). In some embodiments, the DCIAMS is further configured todetermine the set of credentials that can enable authorization to access(e.g., using a set of rules). In 4G10, a proof response is received. Forexample, the proof response comprises a credential retrieved from acredential wallet wherein the credential retrieved from the credentialwallet is based at least in part on rules specified in the proofrequest. In some embodiments, the proof response is signed with anauthentication device private key. In 4G12, it is determined whether theproof response is valid. For example, determining that the proofresponse is valid comprises determining that a credential is not revokedand/or determining that a credential signature is valid by checking thecredential against information stored in the distributed ledger.

In the event it is determined that the proof response is not valid, theprocess ends. In the event it is determined that the proof response isvalid, control passes to 4G14. In 4G14, a session keypair andauthentication token are provided to the user device. For example, theprivate key of the session keypair is encrypted using an authenticationdevice public key and the authentication token is signed using thesession keypair private key. In 4G16, the authentication token isreceived. For example, the authentication token comprises anauthentication response. In 4G18, it is determined whether theauthentication token (e.g., the authentication response) is valid. Inthe event it is determined that the authentication token is not valid,the process ends. In the event it is determined that the authenticationtoken is valid, control passes to 4G20. In 4G20, a login token isgenerated. In 4G22, the login token is provided (e.g., to an applicationsystem).

FIG. 4H is a flow diagram illustrating an embodiment of a process forproviding a session keypair and authentication token to a user device.In some embodiments, the process of FIG. 4H implements 4G14 of FIG. 4G.In the example shown, in 4H00, a session keypair is generated. Forexample, the session keypair is associated with the pairing of the userand the user device. In some embodiments, the session keypair isassociated with a time period, for example, 1 month, 1 week, 1 day, 1hour, 1 minute, etc. In some embodiments, the time period isconfigurable by an administrator of a DCIAMS. In 4H02, an authenticationtoken is signed with the session keypair private key. In 4H04, thesession keypair private key is encrypted with an authentication devicepublic key. In 4H06, the signed authentication token and the encryptedsession keypair private key are encrypted with the user device publickey. In 4H08, the encrypted signed authentication token and encryptedsession keypair private key are provided to the user device. In someembodiments, the encrypted session keypair public key component isstored (e.g., in a storage device for session leases).

FIG. 4I is a flow diagram illustrating an embodiment of a process for acredential challenge. In some embodiments, the process of FIG. 4I isexecuted by DCIAMS 4C00 of FIG. 4C in response to a second request. Inthe example shown, in 4I00, a second request for authorization to accessis received from a second application, wherein access to the secondapplication is requested by the user using the user device. In 4I02, asecond authentication request (e.g., a second U2F authenticationrequest) is provided to the user device. For example, the secondauthentication request (e.g., a U2F challenge) is received from theDCIAMS at the user device. The second authentication request isintercepted by a kernel plugin running on the user device. In someembodiments, the kernel plugin is running at the OS level as aprivileged process, not in the context of any given browser. The kernelplugin is able to detect whether there is a session key (e.g., theencrypted private key component of the session keypair) available, andin the event that there is a session key available, encrypts (using auser device key) a message to a nearby authentication device (e.g., auser's phone) using a proximity communication protocol. In variousembodiments, a proximity communication protocol comprises a Bluetoothprotocol, a near field communication (NFC) protocol, or any otherappropriate communication protocol. The session key as stored on theuser device is encrypted with the authentication device public key sothe user device sends it via the proximity communication protocol to theauthentication device to have the session key decrypted. Theauthentication device returns the session key decrypted to the userdevice and the authentication response (e.g., signed with a private keycomponent of the session keypair) is generated using the decryptedprivate key component of the session key and is passed back to theDCIAMS as the authentication response. The authentication tokencomprises a challenge request/challenge response using U2F. Theauthentication token comprises a split key scenario to unlock thesession key and sign the challenge response. This can be thought of as aserver saying “sign hello” and then being responded to as“signed(hello)”. For example, a user device passes the challenge requestto “sign hello” and the encrypted session private key to authenticationdevice via a proximity communication protocol, so that theauthentication device can automatically produce and return“signed(hello)”. In 4I04, an authentication response comprising anauthentication token is received. For example, the authentication tokenis signed with a private key component of a session keypair. In 4I06, itis determined whether the authentication token is valid. For example,the authentication token is checked to see whether the session keymatches a stored session key on the DCIAMS and that the authenticationtoken is appropriately signed for the U2F challenge response. In theevent it is determined that the authentication token is not valid, theprocess ends. In the event it is determined that the authenticationtoken is valid, control passes to 4I08. In 4I08, a login token isgenerated. For example, the login token enabling access to the secondapplication. In 4I10, the login token is provided. For example, thelogin token is provided the second application.

FIG. 4J is a flow diagram illustrating an embodiment of a process for adigital identity application. In some embodiments, the process of FIG.4J is executed by authentication device 4B00 of FIG. 4B. In 4J00, aproof request challenge is received from the DCIAMS. In 4J02, one ormore credentials that match the request are determined. In 4J04, acredential list is provided to a user for credential selection. In 4J06,it is determined whether a credential is selected. In the event it isdetermined that a credential is not selected, the process ends. In theevent it is determined that a credential is selected, control passes to4J08. In 4J08, a proof response (e.g., comprising the selectedcredential) is created. In 4J10, a request is provided for permission tosign the proof response. In 4J12, it is determined whether permission isreceived to sign the proof response. In the event it is determined thatpermission to sign the proof response is not received, the process ends.In the event it is determined in 4J12 that permission to sign the proofresponse is received, control passes to 4J14. In 4J14, a mobileencryption key is unlocked. In some embodiments, unlocking the mobileencryption key requires an additional authorization, for example,comprising biometric data. In 4J16, an identity key pair private key isdecrypted using the mobile encryption key. In 4J18, the proof responseis signed using the identity key pair private key. In 4J20, the signedproof response is provided. In some embodiments, the signed proofresponse is encrypted using a per channel key.

FIG. 4K is a flow diagram illustrating an embodiment of a process forproviding an authentication token. In some embodiments, the process ofFIG. 4K is executed by authentication device 4B00 of FIG. 4B. In theexample shown, in 4K00, a request comprising an authentication token anda session key encrypted with an authentication device public key andsigned with a user device private key is received. For example, thechallenge request is received via a proximity radio system from the userdevice that includes an encrypted private key component of the sessionkeypair that is encrypted using the authentication device public key andsigned using an a user device private key. In some embodiments, theencrypted private key is for a session, a session private key isencrypted using authentication device public key, and a request fromuser device to the authentication device is signed with user deviceprivate key. In 4K02, it is determined whether the user device signatureis valid. In the event it is determined that the user device signatureis not valid, the process ends. In the event it is determined that theuser device signature is valid, control passes to 4K04. In 4K04, thesession key and authentication token are decrypted. For example, theprivate key component of the session keypair is decrypted. In 4K06, theauthentication token is signed with the session key. For example, theauthentication token is signed using the decrypted private key componentof the session key pair. In 4K08, the signed authentication token isencrypted with the user device public key. In 4K10, the encrypted signedauthentication token is provided to the user device. For example, theencrypted signed authentication token is provided to the user device viaa proximity radio system as the challenge response.

A system for credential authentication includes an interface and aprocessor. The interface is configured to receive a request from anapplication for authorization to access. Access to the application isrequested by a user using a user device. The processor is configured toprovide an authentication request to the user device, receive a devicecredential, wherein the device credential is backed by data stored in adistributed ledger, determine a user identifier and an authenticationdevice associated with the user based at least in part on the devicecredential, provide a proof request to the authentication device,receive a proof response, determine that the proof response is valid,generate a token, and provide the token to the application authorizingaccess for the user. In some embodiments, the authentication requestcomprises a universal second factor authentication request. In someembodiments, the processor is further configured to determine a set ofcredentials that can enable authorization to access. In someembodiments, the set of credentials is determined using rules. In someembodiments, the authentication device includes a credential wallet thatis able to be unlocked by the user. In some embodiments, the credentialwallet is unlocked using a biometric. In some embodiments, a credentialis retrieved from the credential wallet. In some embodiments, the proofresponse includes the credential. In some embodiments, the credentialretrieved from the credential wallet is based at least in part on rulesspecified in the proof request. In some embodiments, the proof responseis signed with an authentication device private key. In someembodiments, determining that the proof response is valid comprises oneor more of the following: determining that a credential is not revokedand/or determining that a credential signature is valid. In someembodiments, the processor is further configured to generate a sessionkeypair for the device and user pairing. In some embodiments, there is atime period associated with the session keypair. In some embodiments,the time period comprises 1 week, 1 day, or 1 hour. In some embodiments,the processor is further configured to store a public key component ofthe session keypair. In some embodiments, the public key component ofthe session keypair is stored in a storage device for session leases. Insome embodiments, the processor is further configured to provide aprivate key component of the session keypair to the user device. In someembodiments, the processor is further configured to encrypt the privatekey component of the session keypair. In some embodiments, the privatekey component of the session keypair is encrypted with an authenticationdevice public key. In some embodiments, the private key component of thesession keypair is encrypted and stored by the user device. In someembodiments, the processor is further configured to provide anauthentication request to the user device comprising a presigned tokenand receive an authentication response from the user device, wherein theauthentication response is signed with a private key component of thesession keypair. In some embodiments, the processor is furtherconfigured to validate the authentication response from the user device,wherein validating the authentication response comprises checking adevice signature of the authentication response. In some embodiments,the token is generated in response to a positive validation of theauthentication response from the user device. In some embodiments, theprocessor is further configured to receive a second request from asecond application for authorization to access, wherein access to thesecond application is requested by the user using the user device. Insome embodiments, processor is further configured to provide a secondauthentication request to the user device. In some embodiments, thesecond authentication request comprises a universal second factorauthentication request. In some embodiments, the processor is furtherconfigured to receive a second authentication response from the userdevice, wherein the second authentication response is signed with aprivate key component of a session keypair. In some embodiments, thesecond authentication response is generated by and provided to the userdevice, wherein the second authentication response is generated by: 1)determining that an encrypted private key component of the sessionkeypair is available; 2) providing the encrypted private key componentof the session keypair to the authentication device using a proximitycommunication protocol for decryption; 3) receiving at theauthentication device a decrypted private key component of the sessionkeypair using the proximity communication protocol; and 4) generatingthe second authentication response that is signed using the private keycomponent of the session keypair. In some embodiments, theauthentication device challenge is provided to the authentication devicevia a proximity communication protocol. In some embodiments, theproximity communication protocol comprises Bluetooth or NFC.

Case E—Digital Credentials for Secondary Factor Authentication

A system for credential authentication includes an interface and aprocessor. The interface is configured to receive a request from anapplication for authorization to access, wherein the access to theapplication is requested by a user using a user device. The processor isconfigured to provide a login request to the user, validate a loginresponse, determine a user authentication device based on the loginresponse, provide a proof request to the user authentication device,receive a proof response, determine that the proof response is validusing a distributed ledger, generate a token, and provide the token tothe application authorizing access for the user.

A system for digital credentials for user device authenticationcomprises a system for credentialing in communication with anapplication system, a user system, and an authentication device. A useruses the user system to access an application on the application system.For example, the user uses a web browser on the user system to access anapplication on the application system. The authentication systemcomprises a system (e.g., a mobile system, a mobile device, asmartphone, etc.) for storing authentication information (e.g., digitalcredentials, encryption keys, etc.) for the user. When the user attemptsto access an application on the application system, the applicationsystem requests authorization to access from the system for digitalcredentials. The system for digital credentials first prompts the userfor login information. For example, the system for digital credentialsprompts the user for a username and password, for biometric information,for a personal identification number (PIN), or for any other appropriatelogin information. When the system for digital credentials receives thelogin information, it validates the login information and determines auser identifier (ID) associated with the login information. The systemfor digital credentials additionally determines an authentication deviceID associated with the user ID. The system for digital credentials thenprovides a proof request to the authentication device associated withthe determined authentication device ID. The proof request comprises arequest for a digital credential that authenticates the access to theapplication system. For example, the proof request comprises a set ofcredentials that are satisfactory for authenticating access to theapplication system. The authentication device receives the proof requestand creates a proof response comprising a digital credential thatsatisfies the proof request. The system for digital credentialsvalidates the proof response using information stored in a distributedledger, and in response to a determination that the proof response isvalid, generates a login token and provides the login token to theapplication system requesting access.

FIG. 5A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 5A comprises anetwork system for a credential system. In the example shown, FIG. 5Acomprises network 5A00. In various embodiments, network 5A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 5A02, distributed ledger 5A04, digital credentialaware identity and access management service 5A06, application system5A08, and user system communicate via network 5A00. Authenticationdevice 5A02 comprises an authentication device associated with a user(e.g., a user of application system 5A08, a user using user system5A10). For example, authentication device 5A02 comprises a computer, asmartphone, a tablet, a mobile device, etc. Distributed ledger 5A04comprises one or more of the following: a decentralized ledger, apermissioned ledger, a public ledger, a blockchain, or any otherappropriate distributed ledger. For example, distributed ledger 5A04 isstored on a plurality of systems and comprises one or more permissionedwriter systems for writing to distributed ledger 5A04. Digitalcredential aware identity and access management service (DCIAMS) 5A06comprises a system for interacting with authentication device 5A02,distributed ledger 5A04, application system 5A08, and any otherappropriate systems. DCIAMS 5A06 comprises a system for coordinating alogin for application system 5A08, for providing a credential toauthentication device 5A02, for requesting a credential fromauthentication device 5A02, for verifying a user identifier or asignature in distributed ledger 5A04, etc. Application system 5A08comprises a system for providing access to an application. For example,application system 5A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system5A10 to access applications on application system 5A08. For example, auser uses an application on user system 5A10 (e.g., a web browser) toconnect to an application on application system 5A08. The application onapplication system 5A08 authenticates a user login before grantingaccess.

DCIAMS 5A06 comprises a system for using a digital credential to performa two factor authenticated login (e.g., a user login to an applicationsystem). For example, DCIAMS 5A06 comprises an interface configured toreceive a request from an application for authorization to access,wherein access to the application is requested by a user using a userdevice, and a processor configured to provide a login request to theuser, validate a login response, determine a user authentication devicebased on the login response, provide a proof request to the userauthentication device, receive a proof response, determine that theproof response is valid (e.g., using information stored in a distributedledger), generate a token, and provide the token to the applicationauthorizing access for the user.

FIG. 5B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 5B00of FIG. 5B comprises authentication device 5A02 of FIG. 1. In theexample shown, authentication device 5B00 comprises interface 5B02. Forexample, interface 5B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 5B04comprises a processor for executing applications 5B06. Applications 5B06comprise digital identity application 5B08 and any other appropriateapplications. Digital identity application 5B08 comprises an applicationfor providing a proof response in response to a proof request. Forexample, digital identity application 5B08 comprises an application forreceiving a proof request challenge from a DCIAMS (e.g., DCIAMS 5A06 ofFIG. 5A), determining one or more credentials that match the request,providing a credential list to a user for credential selection, in theevent it is determined that a credential is selected, creating a proofresponse, providing a request to sign the proof response, and in theevent permission to sign the proof response is received, unlocking amobile encryption key, decrypting an identity key pair private key usingthe mobile encryption key, signing the proof response using the identitykey pair private key, and providing the signed proof response. Secureenclave 5B10 comprises a secure system for storing a mobile encryptionkey. Secure enclave 5B10 comprises mobile encryption key 5B12 andencryption decryption application 5B14. For example, secure enclave 5B10comprises multiple mobile encryption keys, an application for generatingand/or removing mobile encryption keys, etc. Secure enclave 5B10comprises a system for receiving data, transforming it by encryptingand/or decrypting the data using a mobile encryption key or keys, andproviding the transformed data. For example, secure enclave 5B10 isconfigured to only provide transformed input data and not to providemobile encryption key 5B12. In some embodiments, functionality of secureenclave 5B10 is access limited using a biometric (e.g., a fingerprint, aretina scan, a DNA scan, etc.) or a PIN. Authentication device 5B00additionally comprises storage 5B16. Storage 5B16 comprises encryptionkeys 5B18—for example, a public key of an identity key pair, a privatekey of an identity key pair, a private key of an identity key pairencrypted using mobile encryption key 5B12, etc. For example, anidentity key pair of authentication device 5B00 comprises a public keyused by other systems for encrypting data in such a way that it can onlyby decrypted by authentication device 5B00, and a private key fordecrypting data encrypted using the public key or for signing data forproving it came from authentication device 5B00. Storage 5B16additionally comprises digital credentials 5B20, comprising digitalcertificates representing qualifications (e.g., a college degree, workexperience, time living at an apartment, time enrolled in a healthinsurance plan, etc.). Authentication device 5B00 additionally comprisesmemory 5B22. Memory 5B22 comprises executing application data 5B24,comprising data associated with applications 5B06.

FIG. 5C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 5C00 comprises DCIAMS 5A06 of FIG. 5A. In theexample shown DCIAMS 5C00 comprises interface 5C02. For example,interface 5C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. Processor 5C04 comprises aprocessor for executing applications 5C06. Applications 5C06 comprises aset of DCIAMS applications. Decryption application 5C08 comprises anapplication for decrypting encrypted data using a key. Login application5C10 comprises an application for receiving login information (e.g.,username and password, a credential, a quick release (QR) codechallenge, etc.) and providing login credentials (e.g., a login token).Ledger interface application 5C12 comprises an application forinteracting with a distributed ledger (e.g., distributed ledger 5A04 ofFIG. 5A). For example, ledger interface application 5C12 comprises anapplication for verifying a signature in a ledger or checking acredential identifier for revocation in a ledger. Proof requestapplication 5C14 comprises an application for creating a proof request,sending a proof request, evaluating a proof request response (e.g., aproof response), etc. Token generation application 5C16 comprises anapplication for generating a login token (e.g., in response to asuccessful login). Credential issuing application 5C18 comprises anapplication for issuing a digital credential for proving a qualificationin response to a request from a credential issuing authority to issuethe credential. Applications 5C06 additionally comprises any otherappropriate applications. For example, processor 5C04 comprises aprocessor configured to provide a login request to the user, validate alogin response, determine a user authentication device based on thelogin response, provide a proof request to the user authenticationdevice, receive a proof response, determine that the proof response isvalid using a distributed ledger, generate a token, and provide thetoken to the application authorizing access for the user. Storage 5C20comprises user and device database 5C22 and credential rules 5C24. Userand device database 5C22 comprises a database of registered users for agiven customer organization and user details (e.g., username, passwordhash, contact information, email address, relationship to devices,registered public keys, registered mapping documents in a decentralizedledger, etc.). User and device database 5C22 additionally comprises adevice directory comprising all the devices for a given customerorganization as well as mapping documents associated with the devicesand relationships with users associated with the devices. Credentialrules 5C24 comprises a set of credential rules for determining acredential that satisfies a given access request—for example, rulesrelated to a credential associated schema, a credential associatedorganization, a credential issuer, a credential associated location, acredential associated class identifier, a credential associated licensenumber, or any other appropriate credential rules. In variousembodiments, rules comprise rules related to a credential associatedschema, rules related to a credential associated organization, rulesrelated to a credential issuer, rules related to a credential associatedlocation, rules related to a credential associated class identifier oridentifier number, rules related to a credential associated license orlicense number, a credential associated class name, or any otherappropriate credential rules. In some embodiments, the rules are appliedselectively (e.g., based at least in part on a user identifier)—forexample, employees with a credential can access application A,contractors with a credential can access application B, or any otherappropriate matching of access with identifiers. In various embodiments,the rules are applied selectively based at least in part on currentemployment, employee type, location of user, qualification by trainingclass, credential from a third party issuer (e.g., division of motorvehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked). DCIAMS 5C00 additionallycomprises memory 5C26. Memory 5C26 comprises executing application data5C28, comprising data associated with applications 5C06.

FIG. 5D is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 5Dis executed by DCIAMS 5C00 of FIG. 5C. In the example shown, in 5D00, arequest is received from an application for authorization to access,wherein access to the application is requested by a user. In 5D02, alogin request is provided to the user. In 5D04, a login response isreceived. In 5D06, it is determined whether the login response is valid.For example, determining whether the login response is valid comprisespassword hash checking (e.g., using a bcrypt algorithm or an argon2algorithm), validating biometric data, validating a personalidentification number (PIN), etc. In the event it is determined that thelogin response is not valid, the process ends. In the event it isdetermined that the login response is valid, control passes to 5D08. In5D08, a user authentication device is determined based on the loginresponse. In 5D10, a proof request challenge is provided to the userauthentication device. For example, the proof request challengecomprises a request for one or more of a set of credentials (e.g., a setof credentials determined using rules). In 5D12, a proof response isreceived. For example, the proof response comprises a credential of theset of credentials (e.g., a credential stored by the authenticationdevice—for example, a user selected credential) that is checked againsta stored document registered in a distributed ledger. In SD14, it isdetermined whether the proof response is valid. In the event it isdetermined that the proof response is not valid, the process ends. Inthe event it is determined that the proof response is valid, controlpasses to 5D16. In 5D16, a login token is generated. In 5D18, the logintoken is provided.

FIG. 5E is a flow diagram illustrating an embodiment of a process for adigital identity application. In some embodiments, the process of FIG.5E is executed by authentication device 5B00 of FIG. 5B. In 5E00, aproof request challenge is received from the DCIAMS. In 5E02, one ormore credentials that match the request are determined. In 5E04, acredential list is provided to a user for credential selection. In 5E06,it is determined whether a credential is selected. In the event it isdetermined that a credential is not selected, the process ends. In theevent it is determined that a credential is selected, control passes to5E08. In 5E08, a proof response is created. In some embodiments, theproof response comprises a selected credential. In some embodiments, theproof response comprises a document signed with an Identity Private Keycontaining a timestamp of now, indicating they control the DIDreferenced Identity Private Key. In this respect, they don't have anycredentials, but they do control a known key to the distributed ledgerand the DCIAMS which could be considered a second factor as well. Whenusing this approach, however, it is not possible to use the credentialbased rules. In 5E10, a request is provided for permission to sign theproof response. In 5E12, it is determined whether permission is receivedto sign the proof response. In the event it is determined thatpermission to sign the proof response is not received, the process ends.In the event it is determined in 5E12 that permission to sign the proofresponse is received, control passes to 5E14. In 5E14, a mobileencryption key is unlocked. In some embodiments, unlocking the mobileencryption key requires an additional authorization, for example,comprising biometric data. In 5E16, an identity key pair private key isdecrypted using the mobile encryption key. In 5E18, the proof responseis signed using the identity key pair private key. In 5E20, the signedproof response is provided. In some embodiments, the signed proofresponse is encrypted using a per channel key.

FIG. 5F is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 5F implements 5D14 of FIG. 5D. In the example shown, in5F00, a DID document is retrieved from a distributed ledger based ontarget DID in proof response. In 5F02, it is determined whether a publickey from a decentralized ledger matches a DID (e.g., a decentralizedidentifier) in a credential (e.g., a credential of the proof response).In the event it is determined that a public key from a decentralizedledger does not match a DID in the credential, control passes to 5F14.In the event it is determined in 5F02 that that a public key from adecentralized ledger matches a DID in the credential, control passes to5F04. In 5F04, it is determined whether the credential is one of a setof credentials that can enable authorization to access. In the event itis determined that the credential is not one of the set of credentialsthat can enable authorization to access, control passes to 5F14. In theevent it is determined in 5F04 that the credential is one of the set ofcredentials that can enable authorization to access, control passes to5F06. In 5F06, it is determined whether the credential is expired. Inthe event it is determined that the credential is expired, controlpasses to 5F14. In the event it is determined in 5F06 that thecredential is not expired, control passes to 5F08. In 5F08, it isdetermined whether the credential signature is valid. In the event it isdetermined that the credential signature is not valid, control passes to5F14. In the event it is determined in 5F08 that the credentialsignature is valid, control passes to 5F10. In 5F10, it is determinedwhether the credential is revoked. For example, determining that thecredential is revoked comprises querying a revocation registry of arevocation database or a distributed ledger (e.g., a decentralizedledger, a permissioned ledger, a public ledger, a blockchain, etc.) Inthe event that the credential is revoked, control passes to 3G14. In theevent that the credential is not revoked, control passes to 3G12. In3G12, the process indicates that the proof response is valid, and theprocess ends. In 5F14, the process indicates that the proof response isnot valid, and the process ends.

The system for credential authentication comprises an interface and aprocessor. The interface is configured to receive a request from anapplication for authorization to access, wherein access to theapplication is requested by a user using a user device. The processor isconfigured to provide a login request to the user; validate a loginresponse; determine a user authentication device based on the loginresponse; provide a proof request to the user authentication device;receive a proof response; determine that the proof response is validusing a distributed ledger; generate a token; and provide the token tothe application authorizing access for the user. In some embodiments,the login request comprises a username and password request. In someembodiments, the login request comprises a biometric request. In someembodiments, the processor is further configured to receive the loginresponse. In some embodiments, the login response is validated using apassword hash checking. In some embodiments, the password hash checkingcomprises a bcrypt algorithm or an argon2 algorithm. In someembodiments, the processor is further configured to determine a set ofcredentials that can enable authorization to access using rules. In someembodiments, the processor is further configured to generate a proofrequest challenge requesting a credential of the set of credentials. Insome embodiments, the proof response comprises a credential. In someembodiments, the credential comprises a user selected credential. Insome embodiments, the credential comprises a stored credential stored bythe user authentication device. In some embodiments, the proof responseis signed using a user authentication device private key. In someembodiments, the device private key is decrypted using a mobileencryption key. In some embodiments, the mobile encryption key isaccessed using a biometric or a PIN. In some embodiments, determiningthat the proof response is valid comprises determining that a credentialof the proof response satisfies the proof request. In some embodiments,determining that the proof response is valid comprises determining thata credential of the proof response is not expired. In some embodiments,determining that the proof response is valid comprises determining thata credential comprises a valid signature associated with the user. Insome embodiments, determining that the proof response is valid comprisesdetermining that a credential is not revoked. In some embodiments,determining that the credential of the proof response is not revokedcomprises querying a revocation registry of a distributed ledger.

Case F—Digital Credentials for Step-Up Authentication

A system for credential authentication is disclosed. The systemcomprises an interface and a processor. The interface is configured toreceive a request from an application for authorization to access,wherein access to the application is requested by a user, and receive atask request from the application for authorization to access a task,wherein access to the task is requested by the user. The processor isconfigured to authenticate the request from the application forauthorization to access, determine that the task comprises a sensitivetask, determine a user authentication device, provide a challenge for adigital credential to the user authentication device, wherein thedigital credential is backed by data stored in a distributed ledger,receive a response from the user authentication device, determine theresponse is valid, and provide an authorization to access the sensitivetask.

A system for digital credentials for user device authenticationcomprises a system for credential authentication in communication withan application system, a user system, and an authentication device. Auser uses the user system to access an application on the applicationsystem. For example, the user uses a web browser on the user system toaccess an application on the application system. The authenticationsystem comprises a system (e.g., a mobile system, a mobile device, asmartphone, etc.) for storing authentication information (e.g., digitalcredentials, encryption keys, etc.) for the user. When the user attemptsto access an application on the application system, the applicationsystem requests authorization to access from the system for digitalcredentials. The system for digital credentials authenticates the accessusing any appropriate authentication method. As the user then uses theapplication, in the event the user attempts to access a task deemed asensitive task by the application, the application provides a taskrequest to the DCIAMS. The DCIAMS determines whether the task comprisesa sensitive task, and in the event the DCIAMS determines that the taskcomprises a sensitive task, the DCIAMS requires an additionalauthentication before providing authorization to access the sensitivetask. The DCIAMS utilizes either a signature challenge or a credentialchallenge for the additional authentication. In the event the DCIAMSutilizes a signature challenge, the DCIAMS generates a challengedocument and provides the challenge document to the authenticationdevice associated with the user. The authentication device returns thechallenge document to the DCIAMS signed using the authentication deviceprivate key, proving that the user using the authentication deviceprovides permission to access the sensitive task. In the event theDCIAMS utilizes a credential challenge, the DCIAMS determines a set ofcredentials satisfactory to authenticate access to the sensitive taskand provides a proof request challenge requesting a credential to theauthentication device. The authentication device returns a proofresponse to the DCIAMS, proving that the user using the authenticationdevice has the appropriate credentials to access the sensitive task andprovides permission to access the task. When the response is received,the DCIAMS determines whether the response is valid, and in response toa determination that the response is valid, provides an authorization toaccess the sensitive task.

FIG. 6A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 6A comprises anetwork system for a credential system. In the example shown, FIG. 6Acomprises network 6A00. In various embodiments, network 6A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 6A02, distributed ledger 6A04, digital credentialaware identity and access management service (DCIAMS) 6A06, applicationsystem 6A08, and user system communicate via network 6A00.Authentication device 6A02 comprises an authentication device associatedwith a user (e.g., a user of application system 6A08, a user using usersystem 6A10). For example, authentication device 6A02 comprises acomputer, a smartphone, a tablet, a mobile device, etc. Distributedledger 6A04 comprises a distributed ledger (e.g., a permissioned ledger,a decentralized ledger, a public ledger, a blockchain, etc.). Forexample, distributed ledger 6A04 is stored on a plurality of systems andcomprises one or more permissioned writer systems for writing to thedistributed ledger. DCIAMS 6A06 comprises a system for interacting withauthentication device 6A02, distributed ledger 6A04, application system6A08, and any other appropriate systems. DCIAMS 6A06 comprises a systemfor coordinating a login for application system 6A08, for providing acredential to authentication device 6A02, for requesting a credentialfrom authentication device 6A02, for verifying a user identifier or asignature in distributed ledger 6A04, etc. Application system 6A08comprises a system for providing access to an application. For example,application system 6A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system6A10 to access applications on application system 6A08. For example, auser uses an application on user system 6A10 (e.g., a web browser) toconnect to an application on application system 6A08. The application onapplication system 6A08 authenticates a user login before grantingaccess.

DCIAMS 6A06 comprises a system for providing a step-up authenticationfor authenticating access to a sensitive task. For example, DCIAMS 6A06comprises an interface configured to receive a request from anapplication for authorization to access, wherein access to theapplication is requested by a user, and receive a task request from theapplication for authorization to access a task, wherein access to thetask is requested by the user, and a processor configured toauthenticate the request from the application for authorization toaccess, determine that the task comprises a sensitive task, determine auser authentication device, provide a challenge to the userauthentication device, receive a response from the user authenticationdevice, determine the response is valid, and provide an authorization toaccess the sensitive task.

FIG. 6B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 6B00of FIG. 6B comprises authentication device 6A02 of FIG. 6A. In theexample shown, authentication device 6B00 comprises interface 6B02. Forexample, interface 6B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 6B04comprises a processor for executing applications 6B06. Applications 6B06comprise digital identity application 6B08 and any other appropriateapplications. Digital identity application 6B08 comprises an applicationfor providing a proof response in response to a proof request. Forexample, digital identity application 6B08 comprises an application forreceiving a credential challenge from a DCIAMS (e.g., DCIAMS 6A06 ofFIG. 6A), determining a credential request from the credentialchallenge, determining one or more credentials that match the credentialrequest, providing a credential list to a user for credential selection,in the event it is determined that a credential is selected, creating aproof response, providing a request to unlock a mobile encryption key,and in the event permission is received, unlocking a mobile encryptionkey, decrypting an identity key pair private key using the mobileencryption key, signing the proof response using the identity key pairprivate key, and providing the signed proof response. Digital identityapplication 6B08 additionally comprises an application for providing asignature challenge response in response to a signature challengerequest. For example, digital identity application 6B08 comprises anapplication for receiving a signature challenge, unlocking a mobileencryption key (e.g., using a biometric), decrypting a private key usingthe mobile encryption key, signing the signature challenge using theprivate key, encrypting the signed signature challenge (e.g., using aper-channel key), and providing the encrypted signed signaturechallenge.

Secure enclave 6B10 comprises a secure system for storing a mobileencryption key. Secure enclave 6B10 comprises mobile encryption key 6B12and encryption decryption application 6B14. For example, secure enclave6B10 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave6B10 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave6B10 is configured to only provide transformed input data and not toprovide mobile encryption key 6B12. In some embodiments, functionalityof secure enclave 6B10 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) or a personalidentification number (PIN). Authentication device 6B00 additionallycomprises storage 6B16. Storage 6B16 comprises encryption keys 6B18—forexample comprising a public key of an identity key pair, a private keyof an identity key pair, a private key of an identity key pair encryptedusing mobile encryption key 6B12, etc. For example, an identity key pairof authentication device 6B00 comprises a public key used by othersystems for encrypting data in such a way that it can only by decryptedby authentication device 6B00, and a private key for decrypting dataencrypted using the public key or for signing data for proving it camefrom authentication device 6B00. Storage 6B16 additionally comprisesdigital credentials 6B20, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.Authentication device 6B00 additionally comprises memory 6B22. Memory6B22 comprises executing application data 6B24, comprising dataassociated with applications 6B06.

FIG. 6C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 6C00 comprises DCIAMS 6A06 of FIG. 6A. In theexample shown DCIAMS 6C00 comprises interface 6C02. For example,interface 6C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface6C02 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 6C04comprises a processor for executing applications 6C06. Applications 6C06comprise a set of DCIAMS applications. Decryption application 6C08comprises an application for decrypting encrypted data using a key.Login application 6C10 comprises an application for receiving logininformation (e.g., username and password, a credential, a quick response(QR) code challenge, etc.) and providing login credentials (e.g., alogin token). Ledger interface application 6C12 comprises an applicationfor interacting with a distributed ledger (e.g., distributed ledger 6A04of FIG. 6A). For example ledger interface application 6C12 comprises anapplication for verifying a signature by looking up a public key in aledger or checking a credential identifier for revocation in a ledger.Proof request application 6C14 comprises an application for creating aproof request, sending a proof request, evaluating a proof requestresponse (e.g., a proof response), etc. Token generation application6C16 comprises an application for generating a login token (e.g., inresponse to a successful login). Credential issuing application 6C18comprises an application for issuing a digital credential for proving aqualification in response to a request from a credential issuingauthority to issue the credential. Applications 6C06 additionallycomprises any other appropriate applications. For example, processor6C04 comprises a processor configured to authenticate a request from theapplication for authorization to access, determine that a task comprisesa sensitive task, determine a user authentication device, provide achallenge to the user authentication device, receive a response from theuser authentication device, determine the response is valid, and providean authorization to access the sensitive task. Storage 6C20 comprisesuser and device database 6C22 and credential rules 6C24. User and devicedatabase 6C22 comprises a database of registered users for a givencustomer organization and user details (e.g., username, password hash,contact information, email address, relationship to devices, registeredpublic keys, registered mapping documents in a decentralized ledger,etc.). User and device database 6C22 additionally comprises a devicedirectory comprising all the devices for a given customer organizationas well as mapping documents associated with the devices andrelationships with users associated with the devices. Credential rules6C24 comprises a set of credential rules for determining a credentialthat satisfies a given access request, for example rules related to acredential associated schema, a credential associated organization, acredential issuer, a credential associated location, a credentialassociated class identifier, a credential associated license number, orany other appropriate credential rules. In various embodiments, rulescomprise rules related to a credential associated schema, rules relatedto a credential associated organization, rules related to a credentialissuer, rules related to a credential associated location, rules relatedto a credential associated class identifier or identifier number, rulesrelated to a credential associated license or license number, acredential associated class name, or any other appropriate credentialrules. In some embodiments, the rules are applied selectively (e.g.,based at least in part on a user identifier)—for example, employees witha credential can access application A, contractors with a credential canaccess application B, or any other appropriate matching of access withidentifiers. In various embodiments, the rules are applied selectivelybased at least in part on current employment, employee type, location ofuser, qualification by training class, credential from a third partyissuer (e.g., division of motor vehicle license, certification fromschool, etc.), or any other appropriate criterion. As examples ofconfigurable credential rules to grant access: 1) access is granted inthe event that a credential indicates that the holder is a currentemployee (e.g., issuing company is valid, employee status is notexpired, and not revoked); 2) access is granted in the event that acredential indicates that the holder is an employee in an organizationof the company (e.g., issuing company is valid, organization isspecified organization, employee status is not expired, and notrevoked); 3) access is granted in the event that a credential indicatesthat the holder is an employee in a specified location (e.g., issuingcompany is valid, location is a specified location, employee status isnot expired, and not revoked); 4) access is granted in the event that acredential indicates that the holder has necessary training (e.g.,issuing company is valid, training status is complete, employee statusis not expired, and not revoked); and 5) access is granted in the eventthat a credential indicates that the holder has outside credential(e.g., issuing company is valid, outside credential is valid, outsidecredential issuer is third party, employee status is not expired, andnot revoked). DCIAMS 6C00 additionally comprises memory 6C26. Memory6C26 comprises executing application data 6C28, comprising dataassociated with applications 6C06.

FIG. 6D is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 6Dis executed by DCIAMS 6A06 of FIG. 6A. In the example shown, in 6D00, arequest is received from an application for authorization to access,wherein access to the application is requested by a user. In 6D02, therequest from the application for authorization to access isauthenticated. For example, the request for authorization to access isauthenticated using a username and password, a biometric, a credential,a two-factor authentication system, a personal identification number(PIN), etc. In some embodiments, authenticating the request from theapplication for authorization to access comprises providing anindication to the application of authorization to access. For example,authenticating the request from the application for authorization toaccess comprises providing an access token to the application. In 6D04,a task request from the application for authorization to access a taskis received. In some embodiments, the task request from the applicationfor authorization to access a task is received as an encrypted JSONmessage and/or the message is received using a representational statetransfer application programming interface (REST API). For example, thetask comprises a task within the application (e.g., the applicationcomprises a human resources application and the task comprises an editworker salary task). In some embodiments, a signature on the taskrequest from the application for authorization is validated. In 6D06, itis determined whether the task comprises a sensitive task. For example,a sensitive task comprises a task enabling the viewing or modificationof sensitive data, a task only available to a subset of users, a taskundergoing beta testing, etc. In the event it is determined in 6D06 thatthe task does not comprise a sensitive task, control passes to 6D08. In6D08, access is provided to the task, and the process ends. In the eventit is determined in 6D06 that the task comprises a sensitive task,control passes to 6D10. In 6D10, a user authentication device isdetermined. For example, determining a user authentication devicecomprises determining a user identifier based at least in part on therequest from an application for authorization to access and determininga user authentication device from the user identifier. In 6D12, achallenge is provided to the user authentication device. For example,the challenge for the digital credential comprises a challenge documentor a proof request. The digital credential is backed by data stored in adistributed ledger. In some embodiments, the challenge for the digitalcredential to the user authentication device is based at least in parton rules. In some embodiments, the challenge is created based at leastin part on the nature of the sensitive task being accessed. For example,viewing a worker's salary might require that the viewer hold a humanresources administrator credential and/or that the viewer hold a validpersonally identifiable information (PII) trained information technology(IT) worker credential. In 6D14, a response is received from the userauthentication device. In 6D16, it is determined whether the response isvalid. In the event it is determined that the response is not valid, theprocess ends. In the event it is determined that the response is valid,control passes to 6D18. In 6D18, an authorization to access thesensitive task is provided.

FIG. 6E is a flow diagram illustrating an embodiment of a process forproviding a challenge to a user authentication device. In someembodiments, the process of FIG. 6E implements 6D12 of FIG. 6D. In theexample shown, in 6E00, it is determined whether the challenge comprisesa signature challenge or a credential challenge. For example, it isdetermined whether the challenge comprises a signature challenge or acredential challenge based in part on the task, on a sensitivity level,on a user, on an administrator configuration, etc. In the event it isdetermined that the challenge comprises a signature challenge, controlpasses to 6E02. In 6E02, a challenge document is created. For example, achallenge document comprises random data, hash data, a precomputedchallenge document, or any other appropriate challenge document. In6E04, the challenge document is provided. For example, the challengedocument is provided to the user authentication device. In the event itis determined in 6E00 that the challenge comprises a credentialchallenge, control passes to 6E06. In 6E06, a set of credentialssatisfactory to authenticate access to the task is determined. Forexample, the set of credentials satisfactory to authenticate access tothe task is determined using a set of credential rules. In someembodiments, the set of credentials is based at least in part on acontext of the task (e.g., viewing a worker's salary might require thatthe viewer hold a human resources administrator credential and/or thatthe viewer hold a valid personally identifiable information (PII)trained information technology (IT) worker credential, self-serviceviewing of a W2 requires a credential with the same government ID as thedocument is issued to, self-service changing the bank routing details ofwhere an employee paycheck is sent requires a credential given to thatemployee when they started with the employer, etc.) and/or on rules thatenable access. In 6E08, a proof request is created comprising a requestfor a credential of the set of credentials. In 6E10, the proof requestis provided. For example, the proof request is provided to the userauthentication device.

FIG. 6F is a flow diagram illustrating an embodiment of a process fordetermining whether a response is valid. In some embodiments, theprocess of FIG. 6F implements 6D16 of FIG. 6D in the event that thechallenge comprises a signature challenge. In the example shown, in6F00, the response is decrypted. For example, the response istransmitted encrypted with a per-channel key. In 6F02, a responsesignature is validated using an authentication device public key createdover the challenge document. In 6F04, it is determined whether thedocument matches the challenge document (e.g., a challenge documentcreated in 6E02 of FIG. 6E). In the event it is determined that thedocument matches the challenge document, control passes to 6F06. In6F06, an indication is provided that the response is valid, and theprocess ends. In the event it is determined in 6F04 that the documentdoes not match the challenge document, control passes to 6F08. In 6F08,an indication is provided that the response is not valid.

FIG. 6G is a flow diagram illustrating an embodiment of a process fordetermining whether a response is valid. In some embodiments, theprocess of FIG. 6G implements 6D16 of FIG. 6D in the event that thechallenge comprises a credential challenge. In the example shown, in6G00, the response is decrypted. For example, the response istransmitted encrypted with a per-channel key. In 6G02, a credential isdetermined from the response. In 6G04, a DID document is retrieved froma distributed ledger based on target DID in the response.

In 6G06, it is determined whether a public key from a decentralizedledger matches a decentralized identifier (DID) in the credential. Inthe event it is determined that a public key from a distributed ledgerdoes not match a DID in the credential, control passes to 6G18. In theevent it is determined in 6G06 that that a public key from a distributedledger matches a DID in the credential, control passes to 6G08. In 6G08,it is determined whether the credential is one of a set of credentialsthat can enable authorization to access. In the event it is determinedthat the credential is not one of the set of credentials that can enableauthorization to access, control passes to 6G18. In the event it isdetermined in 6G08 that the credential is one of the set of credentialsthat can enable authorization to access, control passes to 6G10. In6G10, it is determined whether the credential is expired. In the eventit is determined that the credential is expired, control passes to 6G18.In the event it is determined in 6G10 that the credential is notexpired, control passes to 6G12. In 6G12, it is determined whether thecredential signature is valid. In the event it is determined that thecredential signature is not valid, control passes to 6G18. In the eventit is determined in 6G12 that the credential signature is valid, controlpasses to 6G14. In 6G14, it is determined whether the credential isrevoked. For example, determining that the credential is revokedcomprises querying a revocation registry of a revocation database or adistributed ledger (e.g., a decentralized ledger, a permissioned ledger,a public ledger, a blockchain, etc.) In the event that the credential isrevoked, control passes to 6G18. In the event that the credential is notrevoked, control passes to 6G16. In 6G16, the process indicates that theresponse is valid, and the process ends. In 6G18, the process indicatesthat the response is not valid, and the process ends.

FIG. 6H is a flow diagram illustrating an embodiment of a process forresponding to a signature challenge. In some embodiments, the process ofFIG. 6H is executed by an authentication device (e.g., authenticationdevice 6A02 of FIG. 6A). In the example shown, in 6H00, a signaturechallenge is received. In 6H02, permission from a user to unlock amobile encryption key is requested. In 6H04, it is determined whetherpermission is received (e.g., whether the user granted permission tounlock the mobile encryption key). For example, a user providingpermission comprises a user providing an indication to grant permission,a user providing login information, a user providing biometricinformation, etc. In the event it is determined that permission is notreceived, the process ends. In the event it is determined thatpermission is received, control passes to 6H06. In 6H06, the mobileencryption key is unlocked. In 6H08, a private key is decrypted usingthe mobile encryption key. In 6H10, the signature challenge is signedusing the private key. For example, the signature challenge is signedusing the identity private key. In 6H12, the signed challenge isencrypted (e.g., using a per-channel key).

FIG. 6I is a flow diagram illustrating an embodiment of a process forresponding to a credential challenge. In some embodiments, the processof FIG. 6I is executed by an authentication device (e.g., authenticationdevice 6A02 of FIG. 6). In the example shown, in 6I00, a credentialchallenge is received. In 6I02, a credential request is determined fromthe credential challenge. In 6I04, one or more credentials that matchthe credential request are determined. In 6I06, a credential list isprovided to a user for selection. In 6I08, it is determined whether acredential is selected. In the event it is determined that a credentialis not selected, the process ends. In the event it is determined that acredential is selected, control passes to 6I10. In 6I10, a proofresponse is created (e.g., comprising the selected credential). In 6I12,permission from a user to unlock a mobile encryption key is requested.In 6I14, it is determined whether permission is received (e.g., from auser to unlock a mobile encryption key). In the event it is determinedthat permission is not received, the process ends. In the event it isdetermined that permission is received, control passes to 6I16. In 6I16,the mobile encryption key is unlocked. In 6I18, a private key isdecrypted using the mobile encryption key. In 6I20, the proof responseis signed using the private key. In 6I22, the signed challenge isencrypted (e.g., using a per-channel key).

FIG. 6J is a flow diagram illustrating an embodiment of a process for anapplication system. In some embodiments, the process of FIG. 6J isexecuted by application system 6A08 of FIG. 6A. In the example shown, in6J00, a request from a user to access an application is received. In6J02, authorization to access is requested. In 6J04, an authenticationof the authorization to access is received. In 6J06, application accessis provided to the user. In 6J08, a request is received from the user toexecute a task. In 6J10, it is determined whether the task comprises asensitive task. In the event the task does not comprise a sensitivetask, control passes to 6J12. In 6J12, access to the task is provided,and the process ends. In the event it is determined in 6J10 that thetask comprises a sensitive task, control passes to 6J14. In 6J14, theuser is prompted to confirm access to the sensitive task. In 6J16, it isdetermined whether the user confirms access to the sensitive task. Inthe event it is determined that the user does not confirm access to thesensitive task, the process ends. In the event it is determined that heuser confirms access to the sensitive task, control passes to 6J18. In6J18, authorization to access the sensitive task is requested. In 6J20,it is determined whether authorization to access the sensitive task isreceived. In the event authorization to access the sensitive task is notreceived, the process ends. In the event authorization to access thesensitive task is received, control passes to 6J22. In 6J22, access tothe sensitive task is provided.

The system comprises an interface and a processor. The interface isconfigured to receive a request from an application for authorization toaccess, wherein access to the application is requested by a user, andreceive a task request from the application for authorization to accessa task, wherein access to the task is requested by the user. Theprocessor is configured to authenticate the request from the applicationfor authorization to access, determine that the task comprises asensitive task, determine a user authentication device, provide achallenge for a digital credential to the user authentication device,wherein the digital credential is backed by data stored in a distributedledger, receive a response from the user authentication device,determine the response is valid, and provide an authorization to accessthe sensitive task. In some embodiments, the challenge for the digitalcredential to the user authentication device is based at least in parton rules. In some embodiments, the task request from the application forauthorization to access the sensitive task is received via an encryptedJSON message. In some embodiments, the application prompts the user toconfirm access to the sensitive task prior to providing the task requestfor authorization to access the sensitive task. In some embodiments,authenticating the request from the application for authorization toaccess comprises providing an access token to the application. In someembodiments, the processor is further configured to validate a signatureon the task request from the application for authorization to access thetask. In some embodiments, the processor is further configured todetermine a user identifier based at least in part on the request froman application for authorization to access. In some embodiments, theprocessor is further configured to determine the user authenticationdevice based at least in part on the user identifier. In someembodiments, the response is encrypted. In some embodiments, theresponse is encrypted with a per-channel key. In some embodiments, theresponse comprises the challenge signed with a user authenticationdevice private key. In some embodiments, the user authentication devicesigns the challenge with the user authentication device private key inresponse to user provided biometric data. In some embodiments,determining the response is valid comprises validating the challengesignature. In some embodiments, the response comprises a credential. Insome embodiments, the credential is selected from a credential wallet.In some embodiments, the challenge to the user authentication devicecomprises a set of credentials for satisfying the challenge. In someembodiments, the set of credentials is based at least in part on acontext of the task and on rules that enable access. In someembodiments, the processor is further configured to access a public keyin a public decentralized ledger and verify the public key correspondsto a decentralized identifier stored by the credential. In someembodiments, determining the response is valid comprises determiningthat the credential is not expired and that the credential comprises avalid signature associated with the user. In some embodiments,determining the response is valid comprises querying a blockchain todetermine that the credential is not revoked.

Case G—Digital Credentials for Access to Sensitive Data

A system for providing access comprises an interface configured toreceive an application access request from an application forauthorization to access, wherein access to the application is requestedby a user, and receive a sensitive data access request from theapplication for authorization to access a document that includessensitive data, wherein access to the document is requested by the user,and a processor configured to determine to authorize access to theapplication in response to the application access request, wherein theauthorizing access includes linking a user authentication device withthe user, determine the user authentication device in response to thesensitive data access request, provide a secondary request forauthorization to access sensitive data to the user authentication devicein response to the sensitive data access request, receive a secondaryrequest response from the user authentication device to the secondaryrequest, and provide the secondary request response to the applicationenabling access to the sensitive data, wherein the document is encryptedfor delivery to the application for the user using a blinding secret andan identity private key.

A system for providing access to sensitive data comprises a digitalcredential aware identity and access management service (DCIAMS) incommunication with an application system and a plurality ofauthentication devices associated with users. A user using a user systemremotely accesses an application on the application system—for example,using a web browser. The user accesses the application to store data,access data, analyze data, execute applications, etc. When the userinitially accesses the application on the application system, a userlogin must be established. For example, the user provides a useridentifier and password, the user provides biometric information, theuser supplies a personal identification number (PIN), etc. Whenutilizing a digital credential for access, the application servercontacts the DCIAMS with user login information. The DCIAMS determinesan authentication device associated with the user and a set ofcredentials satisfactory to authenticate the login, and contacts theauthentication device with a request for a credential. In the event thatthe authentication device satisfactorily provides the credential, theDCIAMS indicates to the application server to allow the user login tothe application.

Once the user has completed login and is utilizing the application onthe application system, a secondary level of confirmation can berequired for access to sensitive data. For example, in the event thatthe user logs into a database application and then leaves their desk, adifferent user should be prevented from accessing secure informationwithin the database application (e.g., social security numbers, taxinformation, personnel review information, etc.). The information alsomust be transmitted securely to prevent its interception. When the userrequests access to a sensitive document, the application responds to theuser system with a request for a blinding secret. For example, theblinding secret comprises an asymmetric encryption key. The user systemcreates the blinding secret and provides the public blinding secret tothe application system. The application system creates a documentencryption key and uses the document encryption key to encrypt thesensitive document. The application system then determines anauthentication system associated with the user and determines a publicencryption key associated with the authentication system. For example,the application system looks up the public key in a public key database,looks up a public key reference in a distributed ledger (e.g., adecentralized ledger, a permissioned ledger, a public ledger, ablockchain, etc.). The application system encrypts the documentencryption key using the authentication device and passes it along withthe blinding secret and the user identifier for the requesting user, tothe DCIAMS. At this point only the user authentication device candecrypt with the document encryption key. The DCIAMS identifies theauthentication device using the user identifier and provides theencrypted document encryption key and the blinding secret to theauthentication device. The authentication device first prompts the userto confirm access to secure data. Since the user always has theauthentication device with them, if an attacker attempts to accesssecure data while they are stepped away from their computer, the processwill be stopped here. For extra security a biometric indicator or a PINcan be used to confirm access, preventing confirmation even if the userhas left their authentication device behind. In the event the userconfirms access, the authentication device decrypts the documentencryption key using its private key, and blinds the document encryptionkey using the blinding secret. The authentication device provides theblinded document encryption key back to the DCIAMS, which provides it tothe application server. The application server provides the blindeddocument encryption key and the encrypted sensitive data to the usersystem. The user system uses the blinding secret it generated to decryptthe document encryption key, and then uses the document encryption keyto decrypt the sensitive document. The user then accesses the sensitivedocument.

FIG. 7A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 7A comprises anetwork system for a credential system. In the example shown, FIG. 7Acomprises network 7A00. In various embodiments, network 7A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 7A02, distributed ledger 7A04, digital credentialaware identity and access management service 7A06, application system7A08, and user system communicate via network 7A00. Authenticationdevice 7A02 comprises an authentication device associated with a user(e.g., a user of application system 7A08, a user using user system7A10). For example, authentication device 7A02 comprises a computer, asmartphone, a tablet, a mobile device, etc. Distributed ledger 7A04comprises a distributed ledger (e.g., a decentralized ledger, apermissioned ledger, a public ledger, a blockchain, etc.). For example,distributed ledger 7A04 is stored on a plurality of systems andcomprises one or more permissioned writer systems for writing to thedistributed ledger. Digital credential aware identity and accessmanagement service (DCIAMS) 7A06 comprises a system for interacting withauthentication device 7A02, distributed ledger 7A04, application system7A08, and any other appropriate systems. DCIAMS 7A06 comprises a systemfor coordinating a login for application system 7A08, for providing acredential to authentication device 7A02, for requesting a credentialfrom authentication device 7A02, for verifying a user identifier or asignature in distributed ledger 7A04, etc. Application system 7A08comprises a system for providing access to an application. For example,application system 7A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system7A10 to access applications on application system 7A08. For example, auser uses an application on user system 7A10 (e.g., a web browser) toconnect to an application on application system 7A08. The application onapplication system 7A08 authenticates a user login before grantingaccess.

DCIAMS 7A06 comprises a system for providing authentication forauthenticating access to sensitive data. For example, DCIAMS 7A06comprises an interface configured to receive an application accessrequest from an application for authorization to access, wherein accessto the application is requested by a user, and receive a sensitive dataaccess request from the application for authorization to access adocument that includes sensitive data, wherein access to the document isrequested by the user, and a processor configured to determine toauthorize access to the application in response to the applicationaccess request, wherein the authorizing access includes linking a userauthentication device with the user, determine the user authenticationdevice in response to the sensitive data access request, provide asecondary request for authorization to access sensitive data to the userauthentication device in response to the sensitive data access request,receive a secondary request response from the user authentication deviceto the secondary request, and provide the secondary request response tothe application.

FIG. 7B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 7B00of FIG. 7B comprises authentication device 7A02 of FIG. 7A. In theexample shown, authentication device 7B00 comprises interface 7B02. Forexample, interface 7B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Processor 7B04comprises a processor for executing applications 7B06. Applications 7B06comprise digital identity application 7B08 and any other appropriateapplications. Digital identity application 7B08 comprises an applicationfor providing a proof response in response to a proof request. Forexample, digital identity application 7B08 comprises an application forreceiving a credential challenge from a DCIAMS (e.g., DCIAMS 7A06 ofFIG. 7A), determining a credential request from the credentialchallenge, determining one or more credentials that match the credentialrequest, providing a credential list to a user for credential selection,in the event it is determined that a credential is selected, creating aproof response, providing a request to unlock a mobile encryption key,and in the event permission is received, unlocking a mobile encryptionkey, decrypting an identity key pair private key using the mobileencryption key, signing the proof response using the identity key pairprivate key, and providing the signed proof response.

Digital identity application 7B08 comprises an application for providinga signature challenge response in response to a signature challengerequest. For example, digital identity application 7B08 comprises anapplication for receiving a signature challenge, unlocking a mobileencryption key (e.g., using a biometric, a PIN, etc.), decrypting aprivate key using the mobile encryption key, signing the signaturechallenge using the private key, encrypting the signed signaturechallenge (e.g., using a per-channel key), and providing the encryptedsigned signature challenge. Digital identity application 7B08additionally comprises an application for responding to a secure datarequest. For example, digital identity application 7B08 comprises anapplication for receiving a secondary request for authorization toaccess sensitive data, requesting permission from a user to unlock amobile encryption key, in the event permission is received unlocking themobile encryption key, decrypting a private key using the mobileencryption key, requesting permission from the user to unlock thesecondary request, in the event permission is received unlocking thesecondary request, accessing an encrypted document encryption key and ablinding secret, decrypting the encrypted document encryption key withthe private key, blinding the document encryption key with the blindingsecret, and providing a secondary request response comprising theblinded document encryption key.

Secure enclave 7B10 comprises a secure system for storing a mobileencryption key. Secure enclave 7B10 comprises mobile encryption key 7B12and encryption decryption application 7B14. For example, secure enclave7B10 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave7B10 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave7B10 is configured to only provide transformed input data and not toprovide mobile encryption key 7B12. In some embodiments, functionalityof secure enclave 7B10 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) and/or a PIN.Authentication device 7B00 additionally comprises storage 7B16. Storage7B16 comprises encryption keys 7B18, for example comprising a public keyof an identity key pair, a private key of an identity key pair, aprivate key of an identity key pair encrypted using mobile encryptionkey 7B12, etc. For example, an identity key pair of authenticationdevice 7B00 comprises a public key used by other systems for encryptingdata in such a way that it can only by decrypted by authenticationdevice 7B00, and a private key for decrypting data encrypted using thepublic key or for signing data for proving it came from authenticationdevice 7B00. Storage 7B16 additionally comprises digital credentials7B20, comprising digital certificates representing qualifications (e.g.,a college degree, work experience, time living at an apartment, timeenrolled in a health insurance plan, etc.). Authentication device 7B00additionally comprises memory 7B22. Memory 7B22 comprises executingapplication data 7B24, comprising data associated with applications7B06.

FIG. 7C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 7C00 comprises DCIAMS 7A06 of FIG. 7A. In theexample shown DCIAMS 7C00 comprises interface 7C02. For example,interface 7C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface7C02 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 7C04comprises a processor for executing applications 7C06. Applications 7C06comprise a set of DCIAMS applications. Decryption application 7C08comprises an application for decrypting encrypted data using a key.Login application 7C10 comprises an application for receiving logininformation (e.g., username and password, a credential, a quick response(QR) code challenge, etc.) and providing login credentials (e.g., alogin token). Ledger interface application 7C12 comprises an applicationfor interacting with a distributed ledger (e.g., distributed ledger 7A04of FIG. 7A). For example ledger interface application 7C12 comprises anapplication for verifying a signature in a ledger or checking acredential identifier for revocation in a ledger. Proof requestapplication 7C14 comprises an application for creating a proof request,sending a proof request, evaluating a proof request response (e.g., aproof response), etc. Token generation application 7C16 comprises anapplication for generating a login token (e.g., in response to asuccessful login). Credential issuing application 7C18 comprises anapplication for issuing a digital credential for proving a qualificationin response to a request from a credential issuing authority to issuethe credential. Applications 7C06 additionally comprise any otherappropriate applications. For example, processor 7C04 comprises aprocessor configured to determine to authorize access to an applicationin response to an application access request, wherein the authorizingaccess includes linking a user authentication device with the user,determine a user authentication device in response to a sensitive dataaccess request, provide a secondary request for authorization to accesssensitive data to the user authentication device in response to thesensitive data access request, receive a secondary request response fromthe user authentication device to the secondary request, and provide thesecondary request response to the application. Storage 7C20 comprisesuser and device database 7C22 and credential rules 7C24. User and devicedatabase 7C22 comprises a database of registered users for a givencustomer organization and user details (e.g., username, password hash,contact information, email address, relationship to devices, registeredpublic keys, registered mapping documents in a distributed ledger,etc.). User and device database 7C22 additionally comprises a devicedirectory comprising all the devices for a given customer organizationas well as mapping documents associated with the devices andrelationships with users associated with the devices. Credential rules7C24 comprises a set of credential rules for determining a credentialthat satisfies a given access request—for example, rules related to acredential associated schema, a credential associated organization, acredential issuer, a credential associated location, a credentialassociated class identifier, a credential associated license number, orany other appropriate credential rules. In various embodiments, rulescomprise rules related to a credential associated schema, rules relatedto a credential associated organization, rules related to a credentialissuer, rules related to a credential associated location, rules relatedto a credential associated class identifier or identifier number, rulesrelated to a credential associated license or license number, acredential associated class name, or any other appropriate credentialrules. In some embodiments, the rules are applied selectively (e.g.,based at least in part on a user identifier)—for example, employees witha credential can access application A, contractors with a credential canaccess application B, or any other appropriate matching of access withidentifiers. In various embodiments, the rules are applied selectivelybased at least in part on current employment, employee type, location ofuser, qualification by training class, credential from a third partyissuer (e.g., division of motor vehicle license, certification fromschool, etc.), or any other appropriate criterion. As examples ofconfigurable credential rules to grant access: 1) access is granted inthe event that a credential indicates that the holder is a currentemployee (e.g., issuing company is valid, employee status is notexpired, and not revoked); 2) access is granted in the event that acredential indicates that the holder is an employee in an organizationof the company (e.g., issuing company is valid, organization isspecified organization, employee status is not expired, and notrevoked); 3) access is granted in the event that a credential indicatesthat the holder is an employee in a specified location (e.g., issuingcompany is valid, location is a specified location, employee status isnot expired, and not revoked); 4) access is granted in the event that acredential indicates that the holder has necessary training (e.g.,issuing company is valid, training status is complete, employee statusis not expired, and not revoked); and 5) access is granted in the eventthat a credential indicates that the holder has outside credential(e.g., issuing company is valid, outside credential is valid, outsidecredential issuer is third party, employee status is not expired, andnot revoked). DCIAMS 7C00 additionally comprises memory 7C26. Memory7C26 comprises executing application data 7C28, comprising dataassociated with applications 7C06.

FIG. 7D is a block diagram illustrating an embodiment of an applicationsystem. In some embodiments, application system 7D00 of FIG. 7Dcomprises application system 7A08 of FIG. 7A. In the example shown,application system 7D00 comprises interface 7D02. For example, interface7D02 comprises an interface for receiving data, providing data,receiving a request for data, etc. Processor 7D04 comprises a processorfor executing applications 7D06. Applications 7D06 comprises databasesystem 7D08 (e.g., application system 7D00 functions as a databasesystem), secure data application 7D10, and other applications 7D10.Secure data application 7D10 comprises an application for encryptingdata, decrypting data, generating encryption keys, or any otherappropriate secure data processes.

For example, secure data application 7D10 comprises an application forreceiving an indication from a user app to access sensitive data,providing a request for a blinding secret to the user app, receiving theblinding secret, generating a document encryption key, encrypting thesensitive data with the document encryption key, determining a publicencryption key for an authentication device associated with the user,providing the blinding secret, the encrypted document encryption key,and a user identifier to a DCIAMS, receiving a blinded documentencryption key, and providing the encrypted sensitive data and theblinded document encryption key to the user app. Other applications 7D12comprise any other appropriate applications (e.g., a communicationsapplication, a chat application, a web browser application, a documentpreparation application, a report preparation application, a userinterface application, a data analysis application, etc.).

Application system 7D00 additionally comprises storage 7D14. Storage7D14 comprises application data storage 7D16, for example comprisingdata stored by applications 7D08. Some data of application data storage7D16 comprises sensitive data. Storage 7D14 additionally comprisesencryption keys 7D18, for example comprising a public key of an identitykey pair, a private key of an identity key pair, public keys of othersystems, one or more document encryption keys, etc. For example, anidentity key pair of application system 7D00 comprises a public key usedby other systems for encrypting data in such a way that it can only bydecrypted by application system 7D00, and a private key for decryptingdata encrypted using the public key or for signing data for proving itcame from application system 7D00. Application system 7D00 additionallycomprises memory 7D20. Memory 7D20 comprises executing application data7D22, comprising data associated with applications 7D06.

FIG. 7E is a block diagram illustrating an embodiment of a user system.In some embodiments, user system 7E00 of FIG. 7E comprises user system7A10 of FIG. 7A. In the example shown, user system 7E00 comprisesinterface 7E02. For example, interface 7E02 comprises an interface forreceiving data, providing data, receiving a request for data, etc.Processor 7E04 comprises a processor for executing applications 7E06.Applications 7E06 comprises web browser application 7E08 (e.g., anapplication for communicating with other systems using a web protocol),secure data application 7E10, and any other appropriate applications.Secure data application 7E10 comprises an application for encryptingdata, decrypting data, generating encryption keys, or any otherappropriate secure data processes.

For example, secure data application 7E10 comprises an application forproviding an indication to access data to an application on anapplication system, receiving a request for a blinding secret,generating the blinding secret, providing the blinding secret to theapplication, in the event the application responds receiving the dataencrypted with a document encryption key and the document encryption keyblinded with the blinding secret, decrypting the document encryption keywith the blinding secret, decrypting the data with the documentencryption key, and accessing the data.

User system 7E00 additionally comprises storage 7E12. Storage 7E12comprises user data storage 7D14—for example comprising any appropriateuser data, and encryption keys 7E16, for example comprising a public keyof an identity key pair, a private key of an identity key pair, publickeys of other systems, etc. For example, an identity key pair of usersystem 7E00 comprises a public key used by other systems for encryptingdata in such a way that it can only by decrypted by user system 7E00,and a private key for decrypting data encrypted using the public key orfor signing data for proving it came from user system 7E00. User system7E00 additionally comprises memory 7E18. Memory 7E18 comprises executingapplication data 7E20, comprising data associated with applications7E06.

FIG. 7F is a flow diagram illustrating an embodiment of a process forproviding access. In some embodiments, the process of FIG. 7F isexecuted by DCIAMS 7A06 of FIG. 7A. In the example shown, in 7F00, anapplication request is received from an application for authorization toaccess, wherein access to the application is requested by a user. In7F02, it is determined whether to authorize access. For example, adetermination of whether to authorize access is made based at least inpart on a user credential, user login information, a user biometric, aPIN, etc. In the event it is determined not to authorize access, theprocess ends. In the event it is determined to authorize access, controlpasses to 7F04. In 7F04, the process authorizes access to theapplication in response to the application access request, wherein theauthorizing access includes linking a user authentication device withthe user. In 7F06, a sensitive data access request is received from theapplication for authorization to access a document that includessensitive data, wherein access to the document is requested by the user.In 7F08, the user authentication device is determined in response to thesensitive data access request. For example, determining the userauthentication device comprises determining the user authenticationdevice linked with the user (e.g., the user authentication device linkedwith the user in 7F04). In some embodiments, determining the userauthentication device linked with the user comprises looking up the linkas stored in a user authentication device database as associated withthe user identifier. In some embodiments, validity of the userauthentication device is determined. For example, the process is furtherconfigured to validate a public key associated with the userauthentication device in a distributed ledger. In some embodiments, thischeck is meant to secure the response from the user authenticationdevice to the DCIAMS and, for example, that the signed response matchesthe registered DID for the user that was challenged. In 7F10, asecondary request for authorization to access sensitive data is providedto the user authentication device in response to the sensitive dataaccess request. For example, the secondary request provided to the userauthentication device for authorization to access sensitive datacomprises a blinding secret, an encrypted document encryption key,and/or a user identifier, wherein the secondary request includes theblinding secret, the encrypted document encryption key, and/or the useridentifier from the sensitive data access request. In some embodiments,the secondary request provided to the user authentication device forauthorization to access sensitive data additionally comprises a filename. In some embodiments, the secondary request provided to the userauthentication device for authorization to access sensitive data isencrypted using a public key associated with the user authenticationdevice. In 7F12, it is determined whether the authentication deviceresponds (e.g., to the secondary request for authorization to accesssensitive data). In the event it is determined that the authenticationdevice does not respond, the process ends. In the event it is determinedthat the authentication device responds, control passes to 7I4. In 7F14,a secondary request response to the secondary request is received fromthe user authentication device. For example, the secondary requestresponse is received via a secure channel. In some embodiments, theprocess is further configured to determine that the secondary requestresponse is valid. In some embodiments, the response is signed with theIdentity Private Key, this signature can then be validated against thecurrent Public Key in the distributed ledger for the user that waschallenged to decrypt the document encryption key. In 7F16, thesecondary request response is provided to the application enablingaccess to the sensitive data, wherein the document is encrypted fordelivery to the application for the user using a blinding secret and anidentity private key. For example, an Identity Private Key is used toprovide greater security and privacy through end-to-end encryption ofuser managed data. End-to-end specifically means creating a mechanism bywhich any intermediate processing systems do not have access to anunencrypted form of the document requested by the user. This isaccomplished by using the combination of a blinding secret and theidentity private key held in an authentication device (e.g., a user'sdigital identity wallet on a user's phone or mobile device). Theblinding mechanism involves a private blinding secret that stays in thebrowser, and a public blinding secret that passes through the flow. Thepublic blinding secret is used to encrypt the result of the mobiledecryption, and then the private blinding secret is used to ultimatelydecrypt the sensitive data. In some embodiments, a blinding secret iscreated by an application (e.g., a browser) on the client system oruser's device (e.g., a laptop). This blinding secret is passedthroughout the system to be used on the authentication device and thenunblinded when it returns to the client system. In some embodiments, theblinding secret comprises a public blinding secret.

In some embodiments, there are other crypto means by which to performthis blinding operation, one involves blinding as a commutativemathematical operation, in which the encrypted document encryption keyis first blinded by encryption code in the browser, then the ‘decrypt’in the mobile device is performed against the blinded value, and passedback through the services. Finally the browser performs the unblindingoperation on the decrypted but still blinded key to arrive at the plaintext for the document encryption key and can then decrypt the data. Thiswould alter the steps described herein, i.e., there would be no blindingthat occurs at the mobile device step, and the mobile device would beblind to the document encryption key as well.

FIG. 7G is a flow diagram illustrating an embodiment of a process for anauthentication device. In some embodiments, the process of FIG. 7G isexecuted by authentication device 7A02 for responding to a secondaryrequest for authorization to access data. In the example shown, in 7G00,a secondary request for authorization to access sensitive data isreceived. In 7G02, permission from a user to unlock a mobile encryptionkey is requested. In 7G04, it is determined whether permission isreceived. In the event it is determined that permission is not received,the process ends. In the event it is determined that permission isreceived, control passes to 7G06. In 7G06, the mobile encryption key isunlocked. In 7G08, a private key is decrypted using the mobileencryption key. In 7G10, permission is requested from the user to unlockthe secondary request. In 7G12, it is determined whether permission isreceived. In the event it is determined that permission is not received,the process ends. In the event it is determined that permission isreceived, control passes to 7G14. In 7G14, the secondary request isunlocked (e.g., using a private key). In 7G16, an encrypted documentencryption key and a blinding secret are accessed. In 7G18, theencrypted document encryption key is decrypted with the private key. In7G20, the document encryption key is blinded with the blinding secret.In 7G22, a secondary request response is provided comprising the blindeddocument encryption key and signed with the identity private key toprove authenticity of response.

FIG. 7H is a flow diagram illustrating an embodiment of a process for anapplication system. In some embodiments, the process of FIG. 7H isexecuted by application system 7A08 of FIG. 7A in response to anindication from a user application to access sensitive data. In theexample shown, in 7H00, an indication from a user application to accesssensitive data is received. For example, the user application comprisesa web browser. In 7H02, a request for a blinding secret is provided tothe user application. In 7H04, the blinding secret is received. In 7H06,a public encryption key for an authentication device associated with theuser is determined. In 7H08, the blinding secret, the encrypted documentencryption key, and a user identifier are provided to the DCIAMS. Forexample, the blinding secret, the encrypted document encryption key, anda user identifier are provided to the DCIAMS via a secure REST call. Insome embodiments, a filename is additionally provided to the DCIAMS. In7H10, it is determined whether the DCIAMS responds. In the event it isdetermined that the DCIAMS does not respond, the process ends. In theevent it is determined that the DCIAMS responds, control passes to 7H12.In 7H12, a blinded document encryption key is received. In 7H14, theencrypted sensitive data and the blinded document encryption key areprovided to the user application.

FIG. 7I is a flow diagram illustrating an embodiment of a process for auser system. In some embodiments, the process of FIG. 7I is executed byuser system 7A10 of FIG. 7A. In the example shown, in 7I00, anindication to access data is provided to an application on anapplication system. In 7I02, a request for a blinding secret isreceived. In 7I04, the blinding secret is generated. In 7I06, theblinding secret is provided to the application. In 7I08, it isdetermined whether the application responds. In the event it isdetermined that the application does not respond, the process ends. Inthe event it is determined that the application responds, control passesto 7I10. In 7I10, the data encrypted with a document encryption key andthe document encryption key blinded with the blinding secret arereceived. In some embodiments, the document encryption key is blindedwith the public blinding secret. In 7I12, the document encryption key isunblinded with the blinding secret. In 7I14, the data is decrypted withthe document encryption key. In 7I16, the data is accessed.

A system for providing access comprises an interface configured toreceive an application access request from an application forauthorization to access, wherein access to the application is requestedby a user, and receive a sensitive data access request from theapplication for authorization to access a document that includessensitive data, wherein access to the document is requested by the user,and a processor configured to determine to authorize access to theapplication in response to the application access request, wherein theauthorizing access includes linking a user authentication device withthe user, determine the user authentication device in response to thesensitive data access request, provide a secondary request forauthorization to access sensitive data to the user authentication devicein response to the sensitive data access request, receive a secondaryrequest response from the user authentication device to the secondaryrequest, and provide the secondary request response to the applicationenabling access to the sensitive data, wherein the document is encryptedfor delivery to the application for the user using a blinding secret andan identity private key. In some embodiments, the sensitive data accessrequest from the application for the authorization to access sensitivedata comprises the blinding secret, an encrypted document encryptionkey, and/or a user identifier, wherein the blinding secret is receivedfrom a user application, and wherein a document encryption key isencrypted to make the encrypted document encryption key using a publickey associated with the user authentication device. In some embodiments,the sensitive data access request from the application for theauthorization to access sensitive data additionally comprises a filename. In some embodiments, the document is encrypted using the documentencryption key, wherein the document is encrypted for securetransmission in response to a user application request for the document.In some embodiments, determining the user authentication devicecomprises determining the user authentication device linked with theuser. In some embodiments, determining the user authentication devicelinked with the user comprises looking up the link as stored in a userauthentication device database as associated with the user identifier.In some embodiments, the sensitive data access request from theapplication for the authorization to access sensitive data istransmitted using a secure REST call. In some embodiments, the secondaryrequest provided to the user authentication device for authorization toaccess sensitive data comprises the blinding secret, an encrypteddocument encryption key, and/or a user identifier, wherein the secondaryrequest includes the blinding secret, the encrypted document encryptionkey, and/or the user identifier from the sensitive data access request.In some embodiments, the secondary request provided to the userauthentication device for authorization to access sensitive dataadditionally comprises a file name. In some embodiments, the secondaryrequest provided to the user authentication device for authorization toaccess sensitive data is encrypted using a public key associated withthe identity private key stored on the user authentication device. Insome embodiments, the user authentication device decrypts the encrypteddocument encryption key to generate a document encryption key. In someembodiments, the document encryption key is blinded using the publicblinding secret to generate a blinded document encryption key. In someembodiments, the user authentication device provides the secondaryrequest response after confirmation from the user, wherein the secondaryrequest response comprises the blinded document encryption key. In someembodiments, the application is configured to provide the blindeddocument encryption key and an encrypted document to a user application,wherein the encrypted document is generated by encrypting the documentwith sensitive data using the document encryption key. In someembodiments, the user application is configured to unblind the blindeddocument encryption key using the blinding secret to generate thedocument encryption key and decrypt the encrypted document using thedocument encryption key to enable the user to access the document withsensitive data. In some embodiments, the user application comprises aweb browser. In some embodiments, wherein the processor is furtherconfigured to validate a public key associated with the userauthentication device in a distributed ledger. In some embodiments, thesecondary request response is received via a secure channel. In someembodiments, the processor is further configured to determine that thesecondary request response is valid.

Case H—Digital Credentials for Employee Badging

A system for credential authentication comprises an interface configuredto receive a create indication to create a badge credential representingan employee badge and receive a claim indication from an authenticationdevice to claim the badge credential, and a processor configured toprovide the badge credential to the authentication device in response tothe claim indication, receive a proof response from the authenticationdevice comprising the badge credential and a lock identifier, validatethe proof response using a distributed ledger, and provide a token forunlocking a lock associated with the lock identifier to theauthentication device.

A system for credential authentication comprises a system for using abadge credential to authenticate access to a door (e.g., for entry to abuilding). When a new user joins an organization, the user installs adigital identity application on a mobile device. The mobile deviceincluding the digital identity application comprises an authenticationdevice for the user. The digital identity application is associated withuser information (e.g., an email address, user identifier (ID), and/or auser account) for identifying the user. The digital identity applicationprovides a request for a badge credential for authenticating entry to adigital credential aware identity and access management service(DCIAMS). When the DCIAMS receives an indication of the new user, theDCIAMS creates a badge credential associated with the user. The DCIAMSreceives the request for the badge credential and provides the badgecredential to the authentication device. When the user attempts to enterthe building, the user places the authentication device in proximity ofa lock system including an automated door lock. The authenticationdevice receives a lock identifier associated with the lock system andprovides a request comprising the badge credential and the lockidentifier to the DCIAMS. The DCIAMS validates the badge credential(e.g., verifying that the badge credential is not expired, not revoked,has a valid signature, etc.) and the lock identifier (e.g., verifyingthat the lock identifier is associated with a valid lock, verifying thatthe user associated with the badge credential has permission to unlockthe lock, verifying that the authentication device associated with thebadge credential has recently communicated with the lock system, etc.).When it is determined that the badge credential and the lock identifierare valid, the DCIAMS creates a token valid for unlocking the lock andprovides the token to the authentication device. The authenticationdevice then provides the token to the lock system for unlocking thelock.

FIG. 8A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 8A comprises anetwork system for a credential system. In the example shown, FIG. 8Acomprises network 8A00. In various embodiments, network 8A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 8A02, distributed ledger 8A04, digital credentialaware identity and access management service 8A06, application system8A08, user system 8A10, and door lock system 8A12 communicate vianetwork 8A00. Authentication device 8A02 comprises an authenticationdevice associated with a user (e.g., a user of application system 8A08,a user using user system 8A10). For example, authentication device 8A02comprises a computer, a smartphone, a tablet, a mobile device, etc.Distributed ledger 8A04 comprises a distributed ledger (e.g., adecentralized ledger, a permissioned ledger, a public ledger, ablockchain, etc.). For example, distributed ledger 8A04 is stored on aplurality of systems and comprises one or more permissioned writersystems for writing to the distributed ledger. DCIAMS 8A06 comprises asystem for interacting with authentication device 8A02, distributedledger 8A04, application system 8A08, and any other appropriate systems.DCIAMS 8A06 comprises a system for coordinating a login for applicationsystem 8A08, for providing a credential to authentication device 8A02,for requesting a credential from authentication device 8A02, forverifying a user identifier or a signature in distributed ledger 8A04,etc. Application system 8A08 comprises a system for providing access toan application. For example, application system 8A08 comprises a systemfor providing access to a database application, a data processingapplication, a productivity application, a communication application,etc. A user uses user system 8A10 to access applications on applicationsystem 8A08. For example, a user uses an application on user system 8A10(e.g., a web browser) to connect to an application on application system8A08. The application on application system 8A08 authenticates a userlogin before granting access. Door lock system 8A12 comprises a computersystem for controlling access to a door lock. For example, door locksystem 8A12 comprises a system for receiving a lock indication andlocking the door lock or receiving an unlock indication and unlockingthe door lock. A lock indication or an unlock indication can require acryptographic token for authenticating the lock or unlock action.Computer systems can communicate with door lock system 8A12 via network8A00 or via a proximity radio system (e.g., Bluetooth, Zigbee, a nearfield communication (NFC) system, etc.). In various embodiments, thedoor lock comprises a door to a building, a gate to a building, a gateto an area, a door for a vehicle, a door for a person, a turnstile, arevolving door, or any other appropriate door.

DCIAMS 8A06 comprises a system for providing authentication forauthenticating access to unlock a door. For example, DCIAMS 8A06comprises an interface configured to receive a create indication tocreate a badge credential representing an employee badge and receive aclaim indication from an authentication device to claim the badgecredential, and a processor configured to provide the badge credentialto the authentication device in response to the claim indication,receive a proof response from the authentication device comprising thebadge credential and a lock identifier, validate the proof responseusing a distributed ledger, and provide a token for unlocking a lockassociated with the lock identifier to the authentication device.

FIG. 8B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 8B00of FIG. 8B comprises authentication device 8A02 of FIG. 8A. In theexample shown, authentication device 8B00 comprises interface 8B02. Forexample, interface 8B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Interface 8B02comprises proximity radio system 8B04. Proximity radio system 8B04comprises a radio system for communication over a short distance. Forexample, proximity radio system 8B04 comprises a wireless system, aBluetooth system, a Zigbee system, an ultra-wideband system, an NFCsystem, an infrared communications system, a wireless personal areanetwork system, etc. Proximity radio system 8B04 comprises a system forcommunicating with a user system, another authentication device, a locksystem, etc. Processor 8B06 comprises a processor for executingapplications 8B08. Applications 8B08 comprise digital identityapplication 8B10 and any other appropriate applications. For example,processor 8B06 comprises a processor for receiving an indication toinstall digital identity application 8B10 and installing digitalidentity application 8B10. Digital identity application 8B10 comprisesan application for providing a proof response in response to a proofrequest. For example, digital identity application 8B10 comprises anapplication for associating with a user email address, requesting abadge credential from a DCIAMS, wherein the request is associated withthe user email address, determining whether the DCIAMS responds, and inthe event that the DCIAMS responds, receiving the badge credential fromthe DCIAMS. Additionally, digital identity application 8B10 comprises anapplication for detecting proximity to a door lock associated with alock identifier, creating a proof response comprising the badgecredential and the lock identifier, providing the proof response to theDCIAMS, determining whether the DCIAMS responds, and in the event thatthe DCIAMS responds, receiving a door unlock token from the DCIAMS andproviding the door unlock token to a door lock system for unlocking thedoor.

Secure enclave 8B12 comprises a secure system for storing a mobileencryption key. Secure enclave 8B12 comprises mobile encryption key 8B14and encryption decryption application 8B16. For example, secure enclave8B12 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave8B12 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave8B12 is configured to only provide transformed input data and not toprovide mobile encryption key 8B14. In some embodiments, functionalityof secure enclave 8B12 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) and/or a personalidentification number (PIN). Authentication device 8B00 additionallycomprises storage 8B18. Storage 8B18 comprises encryption keys 8B20, forexample comprising a public key of an identity key pair, a private keyof an identity key pair, a private key of an identity key pair encryptedusing mobile encryption key 8B14, etc. For example, an identity key pairof authentication device 8B00 comprises a public key used by othersystems for encrypting data in such a way that it can only by decryptedby authentication device 8B00, and a private key for decrypting dataencrypted using the public key or for signing data for proving it camefrom authentication device 8B00. Storage 8B18 additionally comprisesdigital credentials 8B22, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.). Forexample, digital credentials 8B22 comprise a credential wallet. In someembodiments, digital credentials 8B22 comprise a locked digital walletable to be unlocked by a user. For example, digital credentials 8B22 areunlocked using a biometric and/or a PIN. Once the locked digital walletis unlocked, a credential is retrieved. Authentication device 8B00additionally comprises memory 8B24. Memory 8B24 comprises executingapplication data 8B26, comprising data associated with applications8B08.

FIG. 8C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 8C00 comprises DCIAMS 8A06 of FIG. 8A. In theexample shown DCIAMS 8C00 comprises interface 8C02. For example,interface 8C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface8C02 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 8C04comprises a processor for executing applications 8C06. Applications 8C06comprise a set of DCIAMS applications. Decryption application 8C08comprises an application for decrypting encrypted data using a key.Login application 8C10 comprises an application for receiving logininformation (e.g., username and password, a credential, a quick response(QR) code challenge, etc.) and providing login credentials (e.g., alogin token). Ledger interface application 8C12 comprises an applicationfor interacting with a distributed ledger (e.g., distributed ledger 8A04of FIG. 8A). For example ledger interface application 8C12 comprises anapplication for verifying a signature in a ledger or checking a useridentifier for revocation in a ledger. Proof request application 8C14comprises an application for creating a proof request, sending a proofrequest, evaluating a proof request response (e.g., a proof response),etc. Token generation application 8C16 comprises an application forgenerating a login token (e.g., in response to a successful login).Credential issuing application 8C18 comprises an application for issuinga digital credential for proving a qualification in response to arequest from a credential issuing authority to issue the credential.Applications 8C06 additionally comprise any other appropriateapplications.

For example, processor 8C04 comprises a processor for receiving anindication of a new employee associated with an email address, creatinga badge credential for the employee associated with the email address,receiving a request from an authentication device for the credential,determining whether the email address associated with the badgecredential matches the email address associated with the request, and inthe event it is determined that the email address associated with thebadge credential matches the email address associated with the request,providing the badge credential to the authentication device. Processor8C04 additionally comprises a processor for receiving a proof responsefrom an authentication device comprising a badge credential and a lockidentifier, determining whether the proof response is valid, and in theevent it is determined that the proof response is valid determiningwhether the lock identifier is valid, and in the event it is determinedthat the lock identifier is valid, creating a door unlock tokenassociated with the lock identifier, and providing the door unlock tokento the authentication device for unlocking the door.

Storage 8C20 comprises user and device database 8C22 and credentialrules 8C24. User and device database 8C22 comprises a database ofregistered users for a given customer organization and user details(e.g., username, password hash, contact information, email address,relationship to devices, registered public keys, registered mappingdocuments in a decentralized ledger, etc.). User and device database8C22 additionally comprises a device directory comprising all thedevices for a given customer organization as well as mapping documentsassociated with the devices and relationships with users associated withthe devices. Credential rules 8C24 comprises a set of credential rulesfor determining a credential that satisfies a given access request, forexample rules related to a credential associated schema, a credentialassociated organization, a credential issuer, a credential associatedlocation, a credential associated class identifier, a credentialassociated license number, or any other appropriate credential rules. Invarious embodiments, rules comprise rules related to a credentialassociated schema, rules related to a credential associatedorganization, rules related to a credential issuer, rules related to acredential associated location, rules related to a credential associatedclass identifier or identifier number, rules related to a credentialassociated license or license number, a credential associated classname, or any other appropriate credential rules. In some embodiments,the rules are applied selectively (e.g., based at least in part on auser identifier)—for example, employees with a credential can accessapplication A, contractors with a credential can access application B,or any other appropriate matching of access with identifiers. In variousembodiments, the rules are applied selectively based at least in part oncurrent employment, employee type, location of user, qualification bytraining class, credential from a third party issuer (e.g., division ofmotor vehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked). DCIAMS 8C00 additionallycomprises memory 8C26. Memory 8C26 comprises executing application data8C28, comprising data associated with applications 8C06.

FIG. 8D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credentialing. In someembodiments, the process of FIG. 8D is executed by authentication device8A02 of FIG. 8A. In the example shown, in 8D00, an indication isreceived to install a digital identity app. For example, the indicationto install a digital identity app is received as part of a humanresources system employee startup process. In some embodiments, the userreceives a one-time use token by email. In 8D02, the digital identityapp is installed. In 8D04, the digital identity app is associated with auser email address. For example, the token is then invoked opening a webpage with a per-user/per-token quick response code (QR) code that thedigital identity app scans to associate the digital identity app withthe user. In some embodiments, the user's mobile device pushes theone-time use token into the mobile context to start the enrollmentprocess. In 8D06, user is registered with distributed ledger. Forexample, a DID keypair that is associated with the user is generated onthe mobile device and sent to the DCIAMS to be registered as a DIDdocument with the distributed ledger. In some embodiments, registeringwith the distributed ledger also comprises associating the DID keypairwith a badge credential, which is issued by an issuer, registered withthe distributed ledger, and provided to/stored on a user'sauthentication device. In 8D08, a claim indication is provided to claima badge credential from the DCIAMS, wherein the claim indication isassociated with the user. For example, the authentication devicerequests a badge credential from the DCIAMS. The badge credential isassociated with a user (e.g., via an email address, a user ID, a useraccount, etc.). In 8D10, it is determined whether the DCIAMS responds.In the event it is determined that the DCIAMS does not respond, theprocess ends. In the event it is determined that the DCIAMS responds,control passes to 8D12. In 8D12, the badge credential is received fromthe DCIAMS.

FIG. 8E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication. In some embodiments,the process of FIG. 8E is executed by DCIAMS 8A06 of FIG. 8A. In theexample shown, in 8E00, an indication of a new employee associated withan email address is received. In 8E02, a create indication to create abadge credential representing an employee badge is received. Forexample, the create indication is provided to the DCIAMS by a humanresources system employee setup process (e.g., a badge credential iscreated for an employee as part of setting up the employee in the humanresources system). For example, the create indication is associated withan email address. In 8E04, a badge credential is created for theemployee associated with the employee. For example, the badge credentialis created for the employee and registered in the distributed ledgerassociated with the email address received, an employee identifier, anemployee account, etc. In 8E06, a claim indication to claim the badgecredential is received from an authentication device. For example, theclaim indication is associated with an email address. In 8E08, it isdetermined whether the authentication device is associated with thebadge credential. For example, determining whether the authenticationdevice is associated with the badge credential comprises determiningwhether the email address, the user ID (e.g., an IKP), and/or useraccount associated with the badge credential matches information (e.g.,an identifier in the DID document) registered in a distributed ledger.In the event it is determined that the authentication device is notassociated with the badge credential, the process ends. In the event itis determined that the authentication device is associated with thebadge credential, control passes to 8E10. In 8E10, the badge credentialis provided to the authentication device.

FIG. 8F is a flow diagram illustrating an embodiment of a process forunlocking a lock. In some embodiments, the process of FIG. 8F isexecuted by authentication device 8A02 of FIG. 8A. In the example shown,in 8F00, proximity to a lock associated with a lock identifier isdetermined. For example, proximity to the lock is determined using aproximity radio system to determine proximity to a lock systemassociated with the lock. In 8F02, a request is provided to unlock thelock. For example, the request is provided to the lock system associatedwith the lock. In some embodiments, the authentication devicecommunicates with the lock system associated with the lock system via awireless protocol (e.g., Bluetooth or NFC). In 8404, a token request isreceived. For example, the token request is received from the locksystem associated with the lock. In 8F06, a proof response is createdcomprising the badge credential and a signature with the identityprivate key of the DID holder. In 8F08, the proof response and the lockidentifier are provided to the DCIAMS. In 8F10, it is determined whetherthe DCIAMS responds. In the event it is determined that the DCIAMS doesnot respond, the process ends. In the event it is determined that theDCIAMS responds, control passes to 8F12. In 8F12, an unlock token isreceived from the DCIAMS. In 8F14, the unlock token is provided to alock system associated with the lock for unlocking the lock. Forexample, the lock system associated with the lock unlocks the lock inresponse to receiving the token.

FIG. 8G is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 8Gis executed by DCIAMS 8A06 of FIG. 8A. In the example shown, in 8G00, aproof response comprising a badge credential and a lock identifier arereceived from an authentication device. In 8G02, it is determinedwhether the proof response is valid. In the event it is determined thatthe proof response is not valid, the process ends. In the event it isdetermined that the proof response is valid, control passes to 8G04. In8G04, it is determined whether the lock identifier is valid. Forexample, determining whether the lock identifier is valid comprisesverifying that the lock identifier is associated with a valid lock,verifying that the user associated with the badge credential haspermission to unlock the lock, verifying that the authentication deviceassociated with the badge credential has recently communicated with thelock system, etc. In the event it is determined that the lock identifieris not valid, the process ends. In the event it is determined that thelock identifier is valid, control passes to 8G06. In 8G06, an unlocktoken is created associated with the lock identifier. In 8G08, theunlock token is provided to the authentication device for unlocking alock associated with the lock identifier.

FIG. 8H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 8H implements 8G02 of FIG. 8G. In the example shown, in8H00, a DID document is retrieved from distributed ledger based ontarget DID in proof response. In 8H02, it is determined whether a publickey from a decentralized ledger matches a DID (e.g., a decentralizedidentifier) in a badge credential (e.g., the badge credential of theproof response). In the event it is determined that a public key from adecentralized ledger does not match a DID in the badge credential,control passes to 8H14. In the event it is determined in 8H02 that thata public key from a decentralized ledger matches a DID in the badgecredential, control passes to 8H04. In 8H04, it is determined whetherthe badge credential is satisfactory to unlock the lock. In the event itis determined that the badge credential is not satisfactory to unlockthe lock, control passes to 8H14. In the event it is determined in 8H04that the badge credential is satisfactory to unlock the lock, controlpasses to 8H06. In 8H06, it is determined whether the badge credentialis expired. In the event it is determined that the badge credential isexpired, control passes to 8H14. In the event it is determined in 8H06that the badge credential is not expired, control passes to 8H08. In8H08, it is determined whether the badge credential signature is valid.In some embodiments, the badge credential has two signatures, one fromthe original issuer of the credential and one from the holder of thecredential, which are both checked for validity or only one of which ischecked for validity. In the event it is determined that the badgecredential signature is not valid, control passes to 8H14. In the eventit is determined in 8H08 that the badge credential signature is valid,control passes to 8H10. In 8H10, it is determined whether the badgecredential is revoked. For example, determining whether the badgecredential is revoked comprises querying a revocation registry of adistributed ledger (e.g., a public ledger, a decentralized ledger, apermissioned ledger, a blockchain, etc.). In the event it is determinedthat the badge credential is revoked, control passes to 8H14. In theevent it is determined that the badge credential is not revoked, controlpasses to 8H12. In 8H12, the process indicates that the proof responseis valid, and the process ends. In 8H14, the process indicates that theproof response is not valid.

A system for credential authentication comprises an interface configuredto receive a create indication to create a badge credential representingan employee badge and receive a claim indication from an authenticationdevice to claim the badge credential, and a processor configured toprovide the badge credential to the authentication device in response tothe claim indication, receive a proof response from the authenticationdevice comprising the badge credential and a lock identifier, validatethe proof response using a distributed public ledger, and provide atoken for unlocking a lock associated with the lock identifier to theauthentication device. In some embodiments, the create indication tocreate a badge credential is associated with an email address. In someembodiments, the claim indication from the authentication device toclaim the badge credential is associated with an email address. In someembodiments, the processor is further configured to verify the badgecredential is associated with the authentication device. In someembodiments, verifying the badge credential is associated with theauthentication device comprises comparing a badge credential emailaddress with an authentication device email address. In someembodiments, the proof response is received in response to a tokenrequest provided to the authentication device by the lock systemassociated with the lock. In some embodiments, the token request isprovided in response to an authentication device request to unlock thelock. In some embodiments, the authentication device and the lock systemassociated with the lock communicate using a wireless protocol. In someembodiments, the wireless protocol comprises Bluetooth, NFC, or Zigbee.In some embodiments, validating the proof response comprises determiningthat the badge credential is satisfactory to unlock the lock associatedwith the lock identifier. In some embodiments, validating the proofresponse comprises determining that the badge credential comprises avalid signature. In some embodiments, determining that the badgecredential comprises a valid signature comprises querying a distributedledger. In some embodiments, validating the proof response comprisesdetermining that the badge credential is not expired. In someembodiments, validating the proof response comprises determining thatthe badge credential is not revoked. In some embodiments, theauthentication device provides the token to the lock system associatedwith the lock. In some embodiments, the lock system associated with thelock unlocks the lock in response to receiving the token. In someembodiments, the indication to create a badge credential is provided bya human resources system employee startup process. In some embodiments,the claim indication from an authentication device to claim the badgecredential is provided in response to an indication to install a digitalidentity app. In some embodiments, the indication to install a digitalidentity app is in received as part of a human resources system employeestartup process.

Case I—Digital Credentials for Physical Building Access

A system for credential authentication comprises an interface configuredto receive a create indication to create a guest credential representinga guest badge associated with a visitor and receive a claim indicationfrom an authentication device to claim the guest credential, and aprocessor configured to provide the guest credential to theauthentication device in response to the claim indication, provide aproof request to the authentication device, receive a proof responsefrom the authentication device, validate the proof response, determine avisitor tracking system associated with a request from theauthentication device to authenticate entry, and provide a check-inindication to the visitor tracking system that the visitor has checkedin.

A system for credential authentication comprises a system for using aguest credential to authenticate access to a check-in site (e.g., at aphysical location for a guest to check in to a building). When a newuser is invited to visit an organization, a user account and/or useridentifier is established in the system including registering the guestcredential at a distributed ledger. Also, the user installs a digitalidentity application on a mobile device and receives the guestcredential on the mobile device. The mobile device including the digitalidentity application comprises an authentication device for the user.The digital identity application is associated with user information(e.g., an email address, user identifier, user account, etc.) foridentifying the user. The digital identity application provides arequest for a guest credential for authenticating check-in to a digitalcredential aware identity and access management service (DCIAMS). Whenthe DCIAMS receives an indication of the new user, the DCIAMS creates aguest credential associated with the user. The DCIAMS requests a guestcredential and provides the guest credential to an authenticationdevice. When the user attempts to check in at a check-in device (e.g., acheck-in kiosk, a tablet on a receptionist desk, etc.), the user placesthe authentication device in proximity of the check-in device. Theauthentication device receives a check-in site identifier associatedwith the check-in device and provides a request for authentication(e.g., including the check-in site identifier) to the DCIAMS. The DCIAMSresponds to the authentication device with a proof request (e.g., arequest for a credential proving authentication is allowed). Theauthentication device creates a proof response comprising the guestcredential to the DCIAMS. The DCIAMS validates the guest credential(e.g., verifying that the guest credential is not expired, not revoked,has a valid signature, etc.) using the distributed ledger and thecheck-in site identifier (e.g., verifying that the check-in siteidentifier is associated with a valid check-in site, verifying that theuser associated with the guest credential has permission to access thecheck-in site, verifying that the authentication device associated withthe guest credential has recently communicated with the check-in site,etc.). When it is determined that the guest credential and the check-insite identifier are valid, the DCIAMS determines the check-in siteassociated with the request (e.g., from the check-in site identifier)and provides a check-in indication to the visitor tracking system that avisitor has checked in.

FIG. 9A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 9A comprises anetwork system for a credential system. In the example shown, FIG. 9Acomprises network 9A00. In various embodiments, network 9A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 9A02, distributed ledger 9A04, digital credentialaware identity and access management service (DCIAMS) 9A06, applicationsystem 9A08, user system 9A10, visitor tracking system 9A14, andcheck-in site 9A12 communicate via network 9A00. Authentication device9A02 comprises an authentication device associated with a user (e.g., auser of application system 9A08, a user using user system 9A10). Forexample, authentication device 9A02 comprises a computer, a smartphone,a tablet, a mobile device, etc. Distributed ledger 9A04 comprises adistributed ledger (e.g., a permissioned ledger, a public ledger, adecentralized ledger, a blockchain, etc.). For example, distributedledger 9A04 is stored on a plurality of systems and comprises one ormore permissioned writer systems for writing to the distributed ledger.DCIAMS 9A06 comprises a system for interacting with authenticationdevice 9A02, distributed ledger 9A04, application system 9A08, and anyother appropriate systems. DCIAMS 9A06 comprises a system forcoordinating a login for application system 9A08, for providing acredential to authentication device 9A02, for requesting a credentialfrom authentication device 9A02, for verifying a user identifier or asignature in distributed ledger 9A04, etc. Application system 9A08comprises a system for providing access to an application. For example,application system 9A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system9A10 to access applications on application system 9A08. For example, auser uses an application on user system 9A10 (e.g., a web browser) toconnect to an application on application system 9A08. The application onapplication system 9A08 authenticates a user login before grantingaccess. Check-in site 9A12 comprises a computer system for controllingaccess to a guest check-in. For example, check-in site 9A12 comprises acheck-in tablet at a guest entry site. For example, check-in site 9A12comprises a system for receiving a check-in authentication and allowingcheck-in or receiving an indication check-in is not authenticated andnot allowing check-in. Computer systems can communicate with check-insite 9A12 via network 9A00 or via a proximity radio system (e.g.,Bluetooth, Zigbee, near-field communication (NFC), etc.).

DCIAMS 9A06 comprises a system for providing authentication to check inat a check-in site. For example, DCIAMS 9A06 comprises an interfaceconfigured to receive a create indication to create a guest credentialrepresenting a guest badge associated with a visitor and receive a claimindication from an authentication device to claim the guest credential,and a processor configured to provide the guest credential to theauthentication device in response to the claim indication, provide aproof request to the authentication device, receive a proof responsefrom the authentication device, validate the proof response using adistributed ledger, determine a visitor tracking system associated witha request from the authentication device to authenticate entry, andprovide a check-in indication to the visitor tracking system that thevisitor has checked in. Visitor tracking system 9A14 informs a host of aguest arrival by email/text message and/or stores a record ofarrival/departure in a database.

FIG. 9B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 9B00of FIG. 9B comprises authentication device 9A02 of FIG. 9A. In theexample shown, authentication device 9B00 comprises interface 9B02. Forexample, interface 9B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Interface 9B02comprises proximity radio system 9B04. Proximity radio system 9B04comprises a radio system for communication over a short distance. Forexample, proximity radio system 9B04 comprises a wireless system, aBluetooth system, a Zigbee system, an ultrawideband system, an NFCsystem, an infrared communications system, a wireless personal areanetwork system, etc. Proximity radio system 9B04 comprises a system forcommunicating with a user system, another authentication device, a locksystem, etc. Processor 9B06 comprises a processor for executingapplications 9B08. Applications 9B08 comprises digital identityapplication 9B10 and any other appropriate applications. For example,processor 9B06 comprises a processor for receiving an indication toinstall digital identity application 9B10 and installing digitalidentity application 9B10. Digital identity application 9B10 comprisesan application for providing a proof response in response to a proofrequest. For example, digital identity application 9B10 comprises anapplication for associating with a user email address, where the mailsent to the user contains a one-time use token, that token is used tolink a private key on the device to an identity management systemDCIAMS, and then the public key that goes with that private one isregistered in the distributed ledger via a DID document registration.Digital identity application 9B10 also comprises an application forrequesting a guest credential from a DCIAMS, wherein the request isassociated with the user email address or user identifier, determiningwhether the DCIAMS responds, and in the event that the DCIAMS responds,receiving the guest credential from the DCIAMS. Additionally, digitalidentity application 9B10 comprises an application for detectingproximity to a check-in site associated with a check-in site identifier,creating a proof response comprising the guest credential and thecheck-in site identifier, providing the proof response to the DCIAMS,determining whether access is granted, and in the event that access isgranted, receiving check-in access.

Secure enclave 9B12 comprises a secure system for storing a mobileencryption key. Secure enclave 9B12 comprises mobile encryption key 9B14and encryption decryption application 9B16. For example, secure enclave9B12 comprises multiple mobile encryption keys, an application forgenerating and/or removing mobile encryption keys, etc. Secure enclave9B12 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave9B12 is configured to only provide transformed input data and not toprovide mobile encryption key 9B14. In some embodiments, functionalityof secure enclave 9B12 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) or a personalidentification number (PIN). Authentication device 9B00 additionallycomprises storage 9B18. Storage 9B18 comprises encryption keys 9B20—forexample, comprising a public key of an identity key pair, a private keyof an identity key pair, a private key of an identity key pair encryptedusing mobile encryption key 9B14, etc. For example, an identity key pairof authentication device 9B00 comprises a public key used by othersystems for encrypting data in such a way that it can only by decryptedby authentication device 9B00, and a private key for decrypting dataencrypted using the public key or for signing data for proving it camefrom authentication device 9B00. Storage 9B18 additionally comprisesdigital credentials 9B22, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.). Forexample, digital credentials 9B22 comprises a credential wallet. In someembodiments, digital credentials 9B22 comprises a locked digital walletable to be unlocked by a user. For example, digital credentials 9B22 isunlocked using a biometric or a PIN. Once the locked digital wallet isunlocked, a credential is retrieved. Authentication device 9B00additionally comprises memory 9B24. Memory 9B24 comprises executingapplication data 9B26, comprising data associated with applications9B08.

FIG. 9C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 9C00 comprises DCIAMS 9A06 of FIG. 9A. In theexample shown DCIAMS 9C00 comprises interface 9C02. For example,interface 9C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface9C02 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 9C04comprises a processor for executing applications 9C06. Applications 9C06comprises a set of DCIAMS applications. Decryption application 9C08comprises an application for decrypting encrypted data using a key.Login application 9C10 comprises an application for receiving logininformation (e.g., username and password, a credential, a quick response(QR) code challenge, etc.) and providing login credentials (e.g., alogin token). Ledger interface application 9C12 comprises an applicationfor interacting with a distributed ledger (e.g., distributed ledger 9A04of FIG. 8A). For example ledger interface application 9C12 comprises anapplication for verifying a signature in a ledger or checking a useridentifier for revocation in a ledger. Proof request application 9C14comprises an application for creating a proof request, sending a proofrequest, evaluating a proof request response (e.g., a proof response),etc. Token generation application 9C16 comprises an application forgenerating a login token (e.g., in response to a successful login).Credential issuing application 9C18 comprises an application for issuinga digital credential for proving a qualification in response to arequest from a credential issuing authority to issue the credential.Applications 9C06 additionally comprises any other appropriateapplications.

For example, processor 9C04 comprises a processor for receiving anindication of a new guest associated with an email address, receiving acreate indication to create a guest credential representing a guestbadge associated with a guest, creating the guest credential for theguest associated with the email address, receiving a claim indicationfrom an authentication to claim the guest credential, determiningwhether the authentication device is associated with the guestcredential, and in the event it is determined that the authenticationdevice is associated with the guest credential, providing the guestcredential to the authentication device. Processor 9C04 additionallycomprises a processor for receiving a request to authenticate entry froman authentication device, wherein the request comprises a check-in siteidentifier, providing a proof request to the authentication device,receiving a proof response comprising a guest credential, determiningwhether the proof response is valid using a distributed ledger, and inthe event it is determined that the proof response is valid, determiningwhether the check-in site identifier is valid, and in the event thecheck-in site identifier is valid, determining a guest check-in siteassociated with the request to authenticate entry from theauthentication device, and providing a check-in indication to thevisitor tracking system that a visitor has checked in.

Storage 9C20 comprises user and device database 9C22 and credentialrules 9C24. User and device database 9C22 comprises a database ofregistered users for a given customer organization and user details(e.g., username, password hash, contact information, email address,relationship to devices, registered public keys, registered mappingdocuments in a decentralized ledger, etc.). User and device database9C22 additionally comprises a device directory comprising all thedevices for a given customer organization as well as mapping documentsassociated with the devices and relationships with users associated withthe devices. Credential rules 9C24 comprises a set of credential rulesfor determining a credential that satisfies a given access request, forexample rules related to a credential associated schema, a credentialassociated organization, a credential issuer, a credential associatedlocation, a credential associated class identifier, a credentialassociated license number, or any other appropriate credential rules. Invarious embodiments, rules comprise rules related to a credentialassociated schema, rules related to a credential associatedorganization, rules related to a credential issuer, rules related to acredential associated location, rules related to a credential associatedclass identifier or identifier number, rules related to a credentialassociated license or license number, a credential associated classname, or any other appropriate credential rules. In some embodiments,the rules are applied selectively (e.g., based at least in part on auser identifier)—for example, employees with a credential can accessapplication A, contractors with a credential can access application B,or any other appropriate matching of access with identifiers. In variousembodiments, the rules are applied selectively based at least in part oncurrent employment, employee type, location of user, qualification bytraining class, credential from a third party issuer (e.g., division ofmotor vehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked). DCIAMS 9C00 additionallycomprises memory 9C26. Memory 9C26 comprises executing application data9C28, comprising data associated with applications 9C06.

FIG. 9D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication. Insome embodiments, the process of FIG. 9D is executed by authenticationdevice 9A02 of FIG. 9A. In the example shown, in 9D00, an indication toinstall a digital identity app is received. For example, the indicationto install a digital identity app is received as part of a humanresources system guest setup process. In 9D02, the digital identity appis installed. In 9D04, the digital identity app is associated with auser email address. For example, a human resources system guest setupprocess provides a one-time use token (e.g., a hypertext link) deliveredto the email address associated with the user. When the user invokes thelink on a computer (e.g., a laptop or desktop computer) the user isprovided a quick response (QR) code for access by the authenticationdevice. When the authentication device accesses the QR code using thedigital identity app, the digital identity app becomes associated withthe user email address. In some embodiments, the claim indication fromthe authentication device to claim the guest credential comprise aone-time token being used that causes generation of a DID keypair,wherein the private key component is stored on the authentication deviceand the public key component is stored on the distributed ledger, andthat causes providing the guest credential to the authentication device.In the event the user invokes the link using the digital identity app,the token is pushed into the mobile context to associated the digitalidentity app with the user email address. In 9D06, the user isregistered with a distributed ledger. For example, a user, useridentifier, or user account associated with the email address isregistered with a distributed ledger—for example, by invoking a linkthat has been delivered to the email address, scanning a QR code,registering a decentralized identifier (DID) in a distributed ledger,associating the DID with a guest credential, etc. In 9D08, a claimindication is provided to claim a guest credential from the DCIAMS,wherein the claim indication is associated with the user email address,user identifier, or user account. In 9D10, it is determined whether theDCIAMS responds. In the event it is determined that the DCIAMS does notrespond, the process ends. In the event it is determined that the DCIAMSresponds, control passes to 9D12. In 9D12, the guest credential isreceived from the DCIAMS.

FIG. 9E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication. In some embodiments,the process of FIG. 9E is executed by DCIAMS 9A06 of FIG. 9A. In theexample shown, in 9E00, an indication is received of a new guestassociated with an email address. In 9E02, a create indication to createa guest credential representing a guest badge associated with a guest isreceived. For example, the create indication is provided to the DCIAMSby a human resources system employee setup process (e.g., a guestcredential is created for an employee as part of setting up the employeein the human resources system). For example, the create indication isassociated with an email address, a user ID, and/or a user account. In9E04, the guest credential is created for the new guest. For example,the guest credential is created and registered in a distributed ledger.In 9E06, a claim indication is received from an authentication device toclaim the guest credential. In 9E08, it is determined whether theauthentication device is associated with the guest credential. Forexample, determining whether the authentication device is associatedwith the guest credential comprises determining whether the emailaddress, the user ID (e.g., an IKP), and/or the user account associatedwith the guest credential matches information (e.g., an identifier inthe DID document) registered in a distributed ledger. In the event it isdetermined that the authentication device is not associated with theguest credential, the process ends. In the event it is determined thatthe authentication device is associated with the guest credential,control passes to 9E10. In 9E10, the guest credential is provided to theauthentication device.

FIG. 9F is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 9Fis executed by authentication device 9A02 of FIG. 9A. In the exampleshown, in 9F00, proximity to a check-in site associated with a check-insite identifier is determined. For example, proximity to the check-insite is determined using a proximity radio system. In 9F02, a request isprovided to check in at the check-in site (e.g., the request to check inis provided to the check-in site). In some embodiments, theauthentication device communicates with the check-in site via a wirelessprotocol (e.g., Bluetooth, Zigbee, NFC, etc.). In 9F04, a request toauthenticate entry is received from the check-in site. In 9F06, arequest to authenticate entry is provided to the DCIAMS. In 9F08, aproof request is received from the DCIAMS. In 9F10 a proof responsecomprising the guest credential is created. In some embodiments, theproof response is signed (e.g., with an authentication device privatekey). In 9F12, the proof response and the check-in site identifier areprovided to the DCIAMS. In 9F14, it is determined whether access isgranted. In the event it is determined that access is not granted, theprocess ends. In the event it is determined that access is granted,control passes to 9F16. In 9F16, check-in access is received.

FIG. 9G is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 9Gis executed by DCIAMS 9A06 of FIG. 9A. In the example shown, in 9G00, arequest to authenticate entry is received from an authentication device,wherein the request comprises a check-in site identifier. In 9G02, aproof request is provided to the authentication device. In 9G04, a proofresponse comprising a guest credential is received. In 9G06, it isdetermined whether the proof response is valid. For example, the guestcredential is checked against information stored in the distributedledger to determine whether the guest credential is valid—for example,has an appropriate schema, has an appropriate definition, is notexpired, and/or is not revoked. In the event it is determined that theproof response is not valid, the process ends. In the event it isdetermined that the proof response is valid, control passes to 9G08. In9G08, it is determined whether the check-in site identifier is valid.For example, determining that the check-in site identifier is validcomprises verifying that the check-in site identifier is associated witha valid check-in site, verifying that the user associated with the guestcredential has permission to access the check-in site, verifying thatthe authentication device associated with the guest credential hasrecently communicated with the check-in site, etc. In the event it isdetermined that the check-in site identifier is not valid, the processends. In the event it is determined that the check-in site identifier isvalid, control passes to 9G10. In 9G10, a guest check-in site associatedwith the request to authenticate entry from the authentication device isdetermined. In 9G12, a check-in indication is provided to the visitortracking system that a visitor has checked in.

FIG. 9H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 9H implements 9G06 of FIG. 9G. In the example shown, in9H00, a DID document is retrieved from a distributed ledger based ontarget DID in proof response. In 9H02, it is determined whether a publickey from a decentralized ledger matches a DID in a guest credential(e.g., the guest credential of the proof response). In the event it isdetermined that a public key from a decentralized ledger does not matcha DID in the guest credential, control passes to 9H14. In the event itis determined in 9H02 that that a public key from a decentralized ledgermatches a DID in the guest credential, control passes to 9H04. In 9H04,it is determined whether the guest credential is satisfactory toauthenticate check-in. For example, determining whether the guestcredential is satisfactory to authenticate check-in comprisesdetermining whether the guest credential is on a list of guestcredentials certified for visiting, determining whether the visitorassociated with the guest credential has a scheduled appointment,determining whether the visitor associated with the guest credential hasan employee authorization to enter, etc. In the event it is determinedthat the guest credential is not satisfactory to authenticate check-in,control passes to 9H14. In the event it is determined in 9H04 that theguest credential is satisfactory to authenticate check-in, controlpasses to 9H06. In 9H06, it is determined whether the guest credentialis expired. In the event it is determined that the guest credential isexpired, control passes to 9H14. In the event it is determined in 9H06that the guest credential is not expired, control passes to 9H08. In9H08, it is determined whether the guest credential signature is valid.For example, the guest credential signature comprises a signature fromthe credential issuer (e.g., a DCIAMS) or from the credential holder(e.g., the authentication device). In the event it is determined thatthe guest credential signature is not valid, control passes to 9H14. Inthe event it is determined in 9H08 that the guest credential signatureis valid, control passes to 9H10. In 9H10, it is determined whether theguest credential is revoked. For example, determining whether the guestcredential is revoked comprises querying a revocation registry of adistributed ledger (e.g., a decentralized ledger, a permissioned ledger,a public ledger, a blockchain, etc.). In the event it is determined thatthe guest credential is revoked, control passes to 9H14. In 9H14, theprocess indicates that the proof response is not valid., and the processends. In the event it is determined that the guest credential is notrevoked, control passes to 9H12. In 9H12, the process indicates that theproof response is valid, and the process ends.

A system for credential authentication comprises an interface configuredto receive a create indication to create a guest credential representinga guest badge associated with a visitor and receive a claim indicationfrom an authentication device to claim the guest credential, and aprocessor configured to provide the guest credential to theauthentication device in response to the claim indication, provide aproof request to the authentication device, receive a proof responsefrom the authentication device, validate the proof response, determine avisitor tracking system associated with a request from theauthentication device to authenticate entry, and provide a check-inindication to the visitor tracking system that the visitor has checkedin. In some embodiments, the create indication to create a guestcredential is associated with an email address, a user ID, or a useraccount. In some embodiments, the claim indication from theauthentication device to claim the guest credential comprise a one-timetoken being used that causes generation of a DID keypair, wherein theprivate key component is stored on the authentication device and thepublic key component is stored on the distributed ledger, and thatcauses providing the guest credential to the authentication device. Insome embodiments, the processor is further configured to verify theguest credential is associated with the authentication device. In someembodiments, verifying the guest credential is associated with theauthentication device comprises comparing a guest credential emailaddress with an authentication device email address. In someembodiments, the proof request is provided in response to a request toauthenticate entry received from the authentication device. In someembodiments, the request to authenticate entry is provided by theauthentication device in response to an authentication request from theguest check-in site. In some embodiments, the authentication requestfrom the guest check-in site is provided in response to a check-inrequest from the authentication device. In some embodiments, thecheck-in request from the authentication device is providedautomatically upon detection of proximity of the authentication deviceto the guest check-in site. In some embodiments, the authenticationdevice and the guest check-in site communicate using a wirelessprotocol. In some embodiments, the wireless protocol comprisesBluetooth, NFC, or Zigbee. In some embodiments, the request toauthenticate entry from the authentication device comprises a check-insite identifier. In some embodiments, the proof response comprises theguest credential. In some embodiments, the proof response is signed withan authentication device private key. In some embodiments, validatingthe proof response using the distributed ledger comprises determiningthat the guest credential is satisfactory to authenticate check-in,determining that a guest credential signature is valid, determining thatthe guest credential is not expired, or determining that the guestcredential is not revoked. In some embodiments, validating the proofresponse comprises determining that the visitor has a scheduledappointment or an employee authorization to enter. In some embodiments,the create indication to create a guest credential is provided by ahuman resources system guest setup process. In some embodiments, theclaim indication from an authentication device to claim the guestcredential is provided in response to an authentication device digitalidentification app setup. In some embodiments, the authentication devicedigital identification app setup is in response to an email sent as partof a human resources system guest setup process.

Case J—Digital Credentials for Visitor Network Access

A system for credential authentication comprises an interface configuredto receive a create indication to create a visitor network credentialand receive a certify indication to certify an authentication device touse a network, and a processor configured to provide the visitor networkcredential to the authentication device in response to the certifyindication, provide a proof request to the authentication device,receive a proof response, validate the proof response using adistributed ledger, generate a network certificate, and provide thenetwork certificate to the authentication device.

A system for credential authentication comprises a system for using avisitor network credential to authenticate access to a guest network(e.g., a guest wifi network). When a new user is invited to visit anorganization, the user installs a digital identity application on amobile device. The mobile device including the digital identityapplication comprises an authentication device for the user. The digitalidentity application is associated with user information (e.g., an emailaddress, a user identifier (ID), a user account, etc.) for identifyingthe user. The user enrolls in the credential server using a one-time usetoken associated with their email, gets an identity keypair (IKP), andthen uses that IKP from the authentication device to get the credentialfrom the credential server. By signing the request to the credentialserver with the IKP, the platform can find the associated credentialsand also securely release them to the authentication device. The digitalidentity application, after providing the request for a visitor networkcredential for authenticating network access, then receives the visitornetwork credential from the credential server. When the credentialserver receives an indication of the new user, the credential servercreates a visitor network credential associated with the user andregisters the new user and the visitor network credential in adistributed ledger (e.g., a decentralized ledger, a permissioned ledger,a public ledger, a blockchain, etc.). The credential server request forthe visitor network credential and provides the visitor networkcredential to the authentication device. When the user attempts toaccess the network using the authentication device, the network accessdevice provides the authentication device with a captive portal forauthenticating. The captive portal includes a user interface element(e.g., a button) for the user to indicate to authenticate access using adigital credential. When the user indicates to authenticate access usinga digital credential, the authentication device activates a digitalidentity app for accessing the visitor network credential. The user ispresented with a list of available credentials and selects the visitornetwork credential. The digital identity app then provides a certifyindication to a credential server to certify use of the guest wifinetwork. The credential server provides a proof request to the digitalidentity app and the digital identity app provides the credential servera proof response including the network credential. The credential servervalidates the proof response using the distributed ledger, and in theevent the proof response is valid, creates a network certificate forauthentication device. The credential server then provides the networkcertificate to the authentication device. The authentication devicereceives the network certificate and presents the network certificate tothe captive portal for authentication. The captive portal then validatesthe network certificate and creates a network session for theauthentication device. In some embodiments, network session settings forthe authentication device (e.g., available bandwidth, session time,available session connections) are based on user information included inthe network certificate.

FIG. 10A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 10A comprises anetwork system for a credential system. In the example shown, FIG. 10Acomprises network 10A00. In various embodiments, network 10A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 10A02, distributed ledger 10A04, digitalcredential aware identity and access management service (DCIAMS) 10A06,application system 10A08, user system 10A10, and network access device10A12 communicate via network 10A00. Authentication device 10A02comprises an authentication device associated with a user (e.g., a userof application system 10A08, a user using user system 10A10). Forexample, authentication device 10A02 comprises a computer, a smartphone,a tablet, a mobile device, etc. Distributed ledger 10A04 comprises adistributed ledger (e.g., a permissioned ledger, a public ledger, adecentralized ledger, a blockchain, etc.). For example, distributedledger 10A04 is stored on a plurality of systems and comprises one ormore permissioned writer systems for writing to the distributed ledger.DCIAMS 10A06 comprises a system for interacting with authenticationdevice 10A02, distributed ledger 10A04, application system 10A08, andany other appropriate systems. DCIAMS 10A06 comprises a system forcoordinating a login for application system 10A08, for providing acredential to authentication device 10A02, for requesting a credentialfrom authentication device 10A02, for verifying a user identifier or asignature in distributed ledger 10A04, etc. Application system 10A08comprises a system for providing access to an application. For example,application system 10A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system10A10 to access applications on application system 10A08. For example, auser uses an application on user system 10A10 (e.g., a web browser) toconnect to an application on application system 10A08. The applicationon application system 10A08 authenticates a user login before grantingaccess. Network access device 10A12 comprises a system for providingnetwork access. For example, network access device 10A12 comprises aguest wifi access point of an organization. In some embodiments,authentication device 10A02 communicates with network access device10A12 for access to network 10A00. For example, network access device10A12 provides network access at a higher speed, at a lower cost, withgreater security, etc., than authentication device 10A02 is able toachieve on its own. Network access device 10A12 provides network accessto authentication device 10A02 after authentication device 10A12 hasauthenticated access.

DCIAMS 10A06 comprises a system for managing digital credentials forvisitor network access. For example, DCIAMS 10A06 comprises an interfaceconfigured to receive a create indication to create a visitor networkcredential and receive a certify indication to certify an authenticationdevice to use a network, and a processor configured to provide thevisitor network credential to the authentication device in response tothe certify indication, provide a proof request to the authenticationdevice, receive a proof response, validate the proof response using adistributed ledger, generate a network certificate, and provide thenetwork certificate to the authentication device.

FIG. 10B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 10B00of FIG. 10B comprises authentication device 10A02 of FIG. 10A. In theexample shown, authentication device 10B00 comprises interface 10B02.For example, interface 10B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Interface 10B02comprises network access system 10B04. Network access system 10B04comprises a radio system for interacting with a network access device.For example, network access system 10B04 comprises a wifi access system.Processor 10B06 comprises a processor for executing applications 10B08.Applications 10B08 comprise digital identity application 10B10, webbrowser application 10B12 and any other appropriate applications. Forexample, processor 10B06 comprises a processor for receiving anindication to install digital identity application 10B10 and installingdigital identity application 10B10. Digital identity application 10B10comprises an application for providing a proof response in response to aproof request. For example, digital identity application 10B10 comprisesan application for associating with a user email address, a user ID,and/or a user account, registering the email address, the user ID,and/or the user account with a distributed ledger, requesting a visitornetwork credential from a DCIAMS, wherein the request is associated withthe user email address, the user ID, and/or the user account,determining whether the DCIAMS responds, and in the event that theDCIAMS responds, receiving the visitor network credential from theDCIAMS. Additionally digital identity application 10B10 comprises anapplication for receiving a redirect from a captive portal in a webbrowser, receiving an indication to use a visitor network credential,providing a certify indication to a DCIAMS to certify user of a guestwifi network, receiving a proof request from the DCIAMS, providing aproof response, receiving a network certificate, and providing thenetwork certificate to the captive portal. Web browser application 10B12comprises an application for accessing network data using a webprotocol. For example, web browser application 10B12 comprises anapplication for receiving a captive portal for authenticating access toa network.

Secure enclave 10B14 comprises a secure system for storing a mobileencryption key. Secure enclave 10B14 comprises mobile encryption key10B16 and encryption decryption application 10B18. For example, secureenclave 10B14 comprises multiple mobile encryption keys, an applicationfor generating and/or removing mobile encryption keys, etc. Secureenclave 10B14 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave10B14 is configured to only provide transformed input data and not toprovide mobile encryption key 10B16. In some embodiments, functionalityof secure enclave 10B14 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) and/or a personalidentification number (PIN). Authentication device 10B00 additionallycomprises storage 10B20. Storage 10B20 comprises encryption keys10B22—for example, a public key of an identity key pair, a private keyof an identity key pair, a private key of an identity key pair encryptedusing mobile encryption key 10B16, etc. For example, an identity keypair of authentication device 10B00 comprises a public key used by othersystems for encrypting data in such a way that it can only by decryptedby authentication device 10B00, and a private key for decrypting dataencrypted using the public key or for signing data for proving it camefrom authentication device 10B00. Storage 10B20 additionally comprisesdigital credentials 10B24, comprising digital certificates representingqualifications (e.g., a college degree, work experience, time living atan apartment, time enrolled in a health insurance plan, etc.). Forexample, digital credentials 10B24 comprise a credential wallet. In someembodiments, digital credentials 10B24 comprise a locked digital walletable to be unlocked by a user. For example, digital credentials 10B24are unlocked using a biometric or a PIN. Once the locked digital walletis unlocked, a credential is retrieved. Authentication device 10B00additionally comprises memory 10B26. Memory 10B26 comprises executingapplication data 10B28, comprising data associated with applications10B08.

FIG. 10C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 10000 comprises DCIAMS 10A06 of FIG. 10A. Inthe example shown DCIAMS 10000 comprises interface 100O2. For example,interface 100O2 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface100O2 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 10004comprises a processor for executing applications 10006. Applications10006 comprise a set of DCIAMS applications. Decryption application10008 comprises an application for decrypting encrypted data using akey. Login application 10C10 comprises an application for receivinglogin information (e.g., username and password, a credential, a quickresponse (QR) code challenge, etc.) and providing login credentials(e.g., a login token). Ledger interface application 10C12 comprises anapplication for interacting with a distributed ledger (e.g., distributedledger 10A04 of FIG. 10A). For example, ledger interface application10C12 comprises an application for verifying a signature in a ledger orchecking a user identifier for revocation in a ledger. Proof requestapplication 10C14 comprises an application for creating a proof request,sending a proof request, evaluating a proof request response (e.g., aproof response), etc. Token generation application 10C16 comprises anapplication for generating a login token (e.g., in response to asuccessful login). Credential issuing application 10C18 comprises anapplication for issuing a digital credential for proving a qualificationin response to a request from a credential issuing authority to issuethe credential. Applications 10006 additionally comprise any otherappropriate applications.

In the example shown, processor 10004 comprises a processor forreceiving an indication of a new guest associated with an email address,receiving a create indication to create a visitor network credentialrepresenting a network access associated with a guest, creating thevisitor network credential for the guest associated with the emailaddress, receiving a claim indication from an authentication device toclaim the visitor network credential, determining whether theauthentication device is associated with the visitor network credential,and in the event it is determined that the authentication device isassociated with the visitor network credential, providing the visitornetwork credential to the authentication device. Processor 10004additionally comprises a processor for receiving a certify indication tocertify an authentication device to use a network, providing a proofrequest to the authentication device, receiving a proof response,determining whether the proof response is valid using the distributedledger (e.g., by checking that the proof response corresponds to thepreviously registered information in the distributed ledger), and in theevent it is determined that the proof response is valid, generating anetwork certificate and providing the network certificate to theauthentication device.

Storage 10C20 comprises user and device database 10C22 and credentialrules 10C24. User and device database 10C22 comprises a database ofregistered users for a given customer organization and user details(e.g., username, password hash, contact information, email address,relationship to devices, registered public keys, registered mappingdocuments in a decentralized ledger, etc.). User and device database10C22 additionally comprises a device directory comprising all thedevices for a given customer organization as well as mapping documentsassociated with the devices and relationships with users associated withthe devices. Credential rules 10C24 comprises a set of credential rulesfor determining a credential that satisfies a given access request—forexample, rules related to a credential associated schema, a credentialassociated organization, a credential issuer, a credential associatedlocation, a credential associated class identifier, a credentialassociated license number, or any other appropriate credential rules.DCIAMS 10000 additionally comprises memory 10C26. Memory 10C26 comprisesexecuting application data 10C28, comprising data associated withapplications 10006.

FIG. 10D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication. Insome embodiments, the process of FIG. 10D is executed by authenticationdevice 10A02 of FIG. 10A. In the example shown, in 10D00, an indicationto install a digital identity app is received. For example, theindication to install a digital identity app is received as part of ahuman resources system guest setup process. In 10D02, the digitalidentity app is installed. In 10D04, the digital identity app isassociated with a user email address, a user ID, and/or a user account.For example, a human resources system guest setup process provides aone-time use token (e.g., a hypertext link) delivered to the emailaddress associated with the user. When the user invokes the link on acomputer (e.g., a laptop or desktop computer) the user is provided a QRcode for access by the authentication device. When the authenticationdevice accesses the QR code using the digital identity app, the digitalidentity app becomes associated with the user. For example, the digitalidentity app is associated with the user via an email address, a userID, and/or a user account as embodied in a DID document. In the eventthe user invokes the link using the digital identity app, the token ispushed into the mobile context to associate the digital identity appwith the user email address, the user ID, and/or the user account. In10D06, the user is registered with a distributed ledger. For example,registering the user with a distributed ledger comprises invoking a linkthat has been delivered to the email address, scanning a QR code,registering a DID (e.g., a decentralized identifier) in a distributedledger, associating the DID with a visitor network credential,registering the visitor network credential in the distributed ledger,etc. In 10D08, a claim indication is provided to claim a visitor networkcredential from the DCIAMS, wherein the claim indication is associatedwith the user. In 10D10, it is determined whether the DCIAMS responds.In the event it is determined that the DCIAMS does not respond, theprocess ends. In the event it is determined that the DCIAMS responds,control passes to 10D12. In 10D12, the visitor network credential isreceived from the DCIAMS.

FIG. 10E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication. In some embodiments,the process of FIG. 10E is executed by DCIAMS 10A06 of FIG. 10A. In theexample shown, in 10E00, an indication is received of a new guestassociated with an email address. In 10E02, a create indication tocreate a visitor network credential representing a network accessassociated with the new guest is received. For example, the createindication is provided to the DCIAMS by a human resources systememployee setup process (e.g., a visitor network credential is createdfor a guest as part of setting up the guest in the human resourcessystem). For example, the create indication is associated with an emailaddress, a user ID, and/or a user account. In 10E04, the visitor networkcredential is created for the new guest. In 10E06, a claim indication isreceived from an authentication device to claim the visitor networkcredential. In 10E08, it is determined whether the authentication deviceis associated with the visitor network credential. For example,determining whether the authentication device is associated with thevisitor network credential comprises determining whether the emailaddress, the user ID (e.g., an IKP), and/or the user account associatedwith the visitor network credential matches information (e.g., anidentifier in the DID document) registered in a distributed ledger. Inthe event it is determined that the authentication device is notassociated with the visitor network credential, the process ends. In theevent it is determined that the authentication device is associated withthe visitor network credential, control passes to 10E10. In 10E10, thevisitor network credential is provided to the authentication device.

FIG. 10F is a flow diagram illustrating an embodiment of a process foraccessing a network. In some embodiments, the process of FIG. 1OF isexecuted by authentication device 10A02 of FIG. 10A. In the exampleshown, in 10F00, an indication is received that the device is withinrange of a guest wifi network. In 10F02, a user indication is receivedto connect to the guest wifi network. For example, the user indicationis received to connect to the guest wifi network in response to anindication to the user that the device is within range of the guest wifinetwork. In 10F04, a connect indication is provided to connect to theguest wifi network. For example, the connect indication is provided to awifi access point. In 10F06, a captive portal is received. For example,a captive portal comprises an app for authenticating access to the guestwifi network. In some embodiments, the captive portal comprises a usedigital credential user interface object (e.g., a button). In 10F08, anindication is received to use a digital credential. In 10F10, the useris redirected (e.g., by the captive portal) to use a digital credentialsapp (e.g., for providing a digital credential). In 10F12, an indicationis received to use a visitor network credential. For example, thedigital credentials app determines a list of credentials (e.g., a listof credentials on the authentication device, a list of credentials ableto authenticate access to a wifi network, etc.), presents the list ofcredentials to a user, and receives a selection of the visitor networkcredential from the user. In 10F14, a certify indication is provided toa DCIAMS to certify use of the guest wifi network. For example, acertify indication comprises a request for a proof request. In 10F16, aproof request is received from the DCIAMS. In 10F18, a proof response isprovided. For example, the proof response comprises the visitor networkcredential. In 10F20, it is determined whether the DCIAMS responds. Inthe event it is determined that the DCIAMS does not respond, the processends. In the event it is determined that the DCIAMS responds, controlpasses to 10F22. In 10F22, a network certificate is received. Forexample, the network certificate comprises an x509 digital certificate.In some embodiments, since the digital certificates are based onasymmetric cryptography, the network certificate issued would be aPrivate Key and a signed bundle of data around a Public Key that goeswith that private key. Once the authenticator app has this private key,it can use it to sign requests as the certificate holder, includingsigning a request to the captive portal software to prove control. In10F24, the network certificate is provided to the captive portal. In10F26, access (e.g., access to the guest wifi network) is received.

FIG. 10G is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 10Gis executed by DCIAMS 10A06 of FIG. 10A. In the example shown, in 10G00,a certify indication is received to certify an authentication device touse a network. In 10G02, a proof request is provided to theauthentication device. In 10G04, a proof response is received. Forexample, the proof response created using the visitor credential isreceived from the authentication device holding the visitor credential.In 10G06, it is determined whether the proof response is valid. In theevent it is determined that the proof response is not valid, the processends. In the event it is determined that the proof response is valid,control passes to 10G08. In 10G08, a network certificate is generated.For example, the network certificate is based at least in part on avisitor network credential of the proof response, the networkcertificate comprises authentication device identifier data, the networkcertificate comprises user identity data (e.g., user identity data fromthe visitor network credential), etc. In 10G10, the network certificateis provided to the authentication device.

FIG. 10H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 10H implements 10G06 of FIG. 10G. In the example shown,in 10H00, DID document is retrieved from distributed ledger based ontarget DID in proof response. In 10H02, it is determined whether apublic key from a decentralized ledger matches a DID (e.g., adecentralized identifier) in a visitor network credential (e.g., thevisitor network credential of the proof response). In the event it isdetermined that a public key from a decentralized ledger does not matcha DID in the visitor network credential, control passes to 10H14. In theevent it is determined in 10H02 that a public key from a decentralizedledger matches a DID in the visitor network credential, control passesto 10H04. In 10H04, it is determined whether the visitor networkcredential is satisfactory to authenticate network access. For example,determining whether the visitor network credential is satisfactory toauthenticate network access comprises determining whether the visitornetwork credential is on a list of visitor network credentials certifiedfor network access, determining whether the visitor associated with thevisitor network credential is scheduled to be in the network location,determining whether the visitor associated with the visitor networkcredential has an employee authorization to use the network, etc. In theevent it is determined that the visitor network credential is notsatisfactory to authenticate network access, control passes to 10H14. Inthe event it is determined in 10H04 that the visitor network credentialis satisfactory to authenticate network access, control passes to 10H06.In 10H06, it is determined whether the visitor network credential isexpired. In the event it is determined that the visitor networkcredential is expired, control passes to 10H14. In the event it isdetermined in 10H06 that the visitor network credential is not expired,control passes to 10H08. In 10H08, it is determined whether the visitornetwork credential signature is valid. For example, the visitor networkcredential signature comprises a signature from the credential issuer(e.g., a DCIAMS) or from the credential holder (e.g., the authenticationdevice). In the event it is determined that the visitor networkcredential signature is not valid, control passes to 10H14. In the eventit is determined in 10H08 that the visitor network credential signatureis valid, control passes to 10H10. In 10H10, it is determined whetherthe visitor network credential is revoked. For example, determiningwhether the visitor network credential is revoked comprises querying arevocation registry of a distributed ledger (e.g., a permission ledger,a decentralized ledger, a public ledger, a blockchain, etc.). In theevent it is determined that the visitor network credential is revoked,control passes to 10H14. In the event it is determined that the visitornetwork credential is not revoked, control passes to 10H12. In 10H12,the process indicates that the proof response is valid, and the processends. In 10H14, the process indicates that the proof response is notvalid, and the process ends.

FIG. 10I is a flow diagram illustrating an embodiment of a process forauthenticating network access. In some embodiments, the process of FIG.10I is executed by network access device 10A12 of FIG. 10A. In theexample shown, in 10I00, a protected guest wifi network is provided. In10I02, an indication to connect is received (e.g., from anauthentication device). In 10I04, a captive portal app is provided. In10I06, a network certificate is received. In 10I08, it is determinedwhether the network certificate is valid. In the event it is determinedthat the network certificate is not valid, the process ends. In theevent it is determined that the network certificate is valid, controlpasses to 10I10. In 10I10, a set of network session settings aredetermined. For example, network session settings comprise sessionspeed, access to a sandboxed network, or access to a limited set ofconnections. In some embodiments, network session settings aredetermined based at least in part on the network certificate (e.g., onvisitor network credential data of the network certificate, ofauthentication device identifier data of the network certificate, etc.).In 10I12, a network session for the authentication device is created.For example, the network session uses the network session settingsdetermined in 10I12. Creating a network session for the authenticationdevice comprises providing network access to the authentication device.

A system for credential authentication comprises an interface configuredto receive a create indication to create a visitor network credentialand receive a certify indication to certify an authentication device touse a network, and a processor configured to provide the visitor networkcredential to the authentication device in response to the certifyindication, provide a proof request to the authentication device,receive a proof response, validate the proof response using adistributed ledger, generate a network certificate, and provide thenetwork certificate to the authentication device. In some embodiments,the create indication to create the visitor network credential isassociated with an email address. In some embodiments, the interface isfurther configured to receive a claim indication from the authenticationdevice to claim the visitor network credential. In some embodiments, theclaim indication from the authentication device to claim the visitornetwork credential comprises a one-time token being used that causesgeneration of a DID keypair, wherein the private key component is storedon the authentication device and the public key component is stored onthe distributed ledger, and that causes providing the visitor networkcredential to the authentication device. In some embodiments, the claimindication from the authentication device to claim the visitor networkcredential is provided in response to an authentication device digitalidentification app setup. In some embodiments, the authentication devicedigital identification app setup is in response to an email sent as partof a human resources system guest setup process. In some embodiments,the processor is further configured to verify the visitor networkcredential is associated with the authentication device. In someembodiments, verifying the visitor network credential is associated withthe authentication device comprises checking an identifier in a DIDdocument associated with the visitor network credential which areregistered in the distributed ledger. In some embodiments, the certifyindication to certify the authentication device to use the network isreceived from a digital credential app on the authentication device. Insome embodiments, the authentication device provides the certifyindication to certify the authentication device to use the network tothe system for credential authentication in response to a userconfirmation. In some embodiments, the digital credential app isinitiated by a captive portal on the authentication device. In someembodiments, the captive portal is initiated in response to a userattempting to access a network. In some embodiments, validating theproof response using the distributed ledger comprises determining that acredential associated with the proof response satisfies the proofrequest, determining that a proof response signature is valid,determining that the credential associated with the proof response isnot expired, or determining that the credential associated with theproof response is not revoked by looking in the distributed ledger. Insome embodiments, the network certificate comprises an X.509certificate. In some embodiments, the network certificate comprises useridentity data. In some embodiments, the user identity data is based atleast in part on user identity data stored by the visitor networkcredential. In some embodiments, the authentication device returns to acaptive portal for validation of the network certificate. In someembodiments, the captive portal creates a network session for theauthentication device. In some embodiments, network session settings arebased at least in part on the network certificate. In some embodiments,the network session settings comprise session speed, access to asandboxed network, or access to a limited set of connections. In someembodiments, the create indication to create the visitor networkcredential is provided by a human resources system guest setup process.

Case K—Digital Credentials for Location Aware Check In

A system for credential authentication comprises an interface configuredto receive a create indication to create a location aware credential,wherein the location aware credential specifies visit location data andreceive a check in indication to check in from an authentication device,wherein the authentication device provides the check in indication tocheck in in response to determining that a detected location is within ageographic boundary designated in the visit location data of thelocation aware credential, and a processor configured to provide a proofrequest, receive a proof response, validate the proof response using adistributed ledger, and provide a success indication of successful checkin.

A system for credential authentication comprises a system for using alocation aware credential to authenticate a location aware check in. Thelocation aware credential enables an authentication device to monitorits location and automatically initiate a check-in to a locationrequiring authorization based on visit locations specified in thelocation aware credential. When a new user is invited to visit anorganization, a user account and/or user identifier is established inthe system including registering the location aware credential at adistributed ledger. Also, the user installs a digital identityapplication on a mobile device and receives the location awarecredential on the mobile device. The mobile device including the digitalidentity application comprises an authentication device for the user.The digital identity application is associated with user information(e.g., an email address, a user identifier (ID), a user account, etc.)for identifying the user. The digital identity application provides arequest for a location aware credential for authenticating networkaccess to a digital credential aware identity and access managementservice (DCIAMS). When the DCIAMS receives an indication of the newuser, the DCIAMS creates a location aware credential associated with theuser. For example, the location aware credential specifies visitlocation data comprising a location, set of locations, geofenceboundary, etc. within which it is valid. The DCIAMS request for thelocation aware credential and provides the location aware credential tothe authentication device. When the authentication device enters ageographic boundary with an unexpired location aware credential, theauthentication device indicates that the process for check in shouldbegin. The authentication device verifies that the location awarecredential is not expired at the current date and time and provides acheck in indication to the DCIAMS. The DCIAMS provides a proof requestcomprising a request for the location aware credential and theauthentication device provides a proof response comprising thecredential. The DCIAMS validates the credential (e.g., verifying thatthe guest credential is not expired, not revoked, has a valid signature,etc.) using the distributed ledger, and in response to determining thatthe credential is valid, provides an indication of success (e.g., to theauthentication device, to a visitor host, to a visitor tracking system,etc.). In some embodiments, the credential server additionally providesa location specific message to the user.

FIG. 11A is a block diagram illustrating an embodiment of a networksystem. In some embodiments, the network system of FIG. 11A comprises anetwork system for a credential system. In the example shown, FIG. 11Acomprises network 11A00. In various embodiments, network 11A00 comprisesone or more of the following: a local area network, a wide area network,a wired network, a wireless network, the Internet, an intranet, astorage area network, or any other appropriate communication network.Authentication device 11A02, distributed ledger 11A04, DCIAMS 11A06,application system 11A08, user system 11A10, and network access device11A12 communicate via network 11A00. Authentication device 11A02comprises an authentication device associated with a user (e.g., a userof application system 11A08 and/or a user using user system 11A10). Forexample, authentication device 11A02 comprises a computer, a smartphone,a tablet, a mobile device, etc. Distributed ledger 11A04 comprises adistributed ledger (e.g., a decentralized ledger, a permissioned ledger,a public ledger, a blockchain, etc.). For example, distributed ledger11A04 is stored on a plurality of systems and comprises one or morepermissioned writer systems for writing to the distributed ledger.DCIAMS 11A06 comprises a system for interacting with authenticationdevice 11A02, distributed ledger 11A04, application system 11A08, andany other appropriate systems. DCIAMS 11A06 comprises a system forcoordinating a login for application system 11A08, for providing acredential to authentication device 11A02, for requesting a credentialfrom authentication device 11A02, for verifying a user identifier or asignature in distributed ledger 11A04, etc. Application system 11A08comprises a system for providing access to an application. For example,application system 11A08 comprises a system for providing access to adatabase application, a data processing application, a productivityapplication, a communication application, etc. A user uses user system11A10 to access applications on application system 11A08. For example, auser uses an application on user system 11A10 (e.g., a web browser) toconnect to an application on application system 11A08. The applicationon application system 11A08 authenticates a user login before grantingaccess.

DCIAMS 11A06 comprises a system for digital credentials for locationaware check in. For example, DCIAMS 11A06 comprises an interfaceconfigured to receive a create indication to create a location awarecredential, wherein the credential specifies visit location data, andreceive a check in indication to check in from an authentication device,wherein the authentication device provides the check in indication tocheck in in response to determining that a detected location is within ageographic boundary designated in the visit location data of thelocation aware credential, and a processor configured to provide a proofrequest, receive a proof response, validate the proof response using adistributed ledger, and provide a success indication of successful checkin.

FIG. 11B is a block diagram illustrating an embodiment of anauthentication device. In some embodiments, authentication device 11B00of FIG. 11B comprises authentication device 11A02 of FIG. 11A. In theexample shown, authentication device 11B00 comprises interface 11B02.For example, interface 11B02 comprises an interface for receiving data,providing data, receiving a request for data, etc. Authentication device11B00 additionally comprises location detection system 11B04. Locationdetection system 11B04 comprises a location detection system fordetecting a detected location. For example, location detection system11B04 comprises a global positioning system (e.g., a GPS). Processor11B06 comprises a processor for executing applications 11B08.Applications 11B08 comprise digital identity application 11B10 and anyother appropriate applications. For example, processor 11B06 comprises aprocessor for receiving an indication to install digital identityapplication 11B10 and installing digital identity application 11B10.Digital identity application 11B10 comprises an application forproviding a proof response in response to a proof request.

For example, digital identity application 11B10 comprises an applicationfor associating with a user email address, where the mail sent to usecontains a one-time use token, that token is used to link a private keyon the device to an identity management system DCIAMS, and then thepublic key that goes with that private one is registered in thedistributed ledger via a DID document registration. Digital identityapplication 11B10 also comprises an application for providing a claimindication to claim a location aware credential from the DCIAMS, whereinthe claim indication is associated with the user email address, user ID,and/or user account, determining whether the DCIAMS responds, and in theevent that the DCIAMS responds, receiving the location aware credentialfrom the DCIAMS. Additionally, digital identity application 11B10comprises an application for determining whether a detected location iswithin a geographic boundary designated by the location awarecredential, in response to a determination that the detected location ofthe authentication device is within a geographic boundary, determiningwhether a location aware credential is unexpired at the current time, inresponse to a determination that a location aware credential isunexpired at the current time, providing a check in prompt to a user,determining whether the user accepts the prompt to check in, in responseto a determination that the user accepts the prompt to check in,providing an indication to check in to the DCIAMS, receiving a proofrequest from the DCIAMS, providing a proof response to the DCIAMS,determining whether the DCIAMS responds, in response to a determinationthat the DCIAMS responds, receiving a success indication and receiving alocation specific message.

Secure enclave 11B12 comprises a secure system for storing a mobileencryption key. Secure enclave 11B12 comprises mobile encryption key11B14 and encryption decryption application 11B16. For example, secureenclave 11B12 comprises multiple mobile encryption keys, an applicationfor generating and/or removing mobile encryption keys, etc. Secureenclave 11B12 comprises a system for receiving data, transforming it byencrypting and/or decrypting the data using a mobile encryption key orkeys, and providing the transformed data. For example, secure enclave11B12 is configured to only provide transformed input data and not toprovide mobile encryption key 11B14. In some embodiments, functionalityof secure enclave 11B12 is access limited using a biometric (e.g., afingerprint, a retina scan, a DNA scan, etc.) or a personalidentification number. Authentication device 11B00 additionallycomprises storage 11B18. Storage 11B18 comprises encryption keys 11B20,for example comprising a public key of an identity key pair, a privatekey of an identity key pair, a private key of an identity key pairencrypted using mobile encryption key 11B14, etc. For example, anidentity key pair of authentication device 11B00 comprises a public keyused by other systems for encrypting data in such a way that it can onlyby decrypted by authentication device 11B00, and a private key fordecrypting data encrypted using the public key or for signing data forproving it came from authentication device 11B00. Storage 11B18additionally comprises digital credentials 11B22, comprising digitalcertificates representing qualifications (e.g., a college degree, workexperience, time living at an apartment, time enrolled in a healthinsurance plan, etc.). For example, digital credentials 11B22 comprisesa credential wallet. In some embodiments, digital credentials 11B22comprises a locked digital wallet able to be unlocked by a user. Forexample, digital credentials 11B22 is unlocked using a biometric or apersonal identification number (PIN). Once the locked digital wallet isunlocked, a credential is retrieved. Authentication device 11B00additionally comprises memory 11B24. Memory 11B24 comprises executingapplication data 11B26, comprising data associated with applications11B08.

FIG. 11C is a block diagram illustrating an embodiment of a digitalcredential aware identity and access management service (DCIAMS). Insome embodiments, DCIAMS 11C00 comprises DCIAMS 11A06 of FIG. 11A. Inthe example shown DCIAMS 11C00 comprises interface 11C02. For example,interface 11C02 comprises an interface for receiving data, providingdata, receiving a request for data, etc. In some embodiments, interface11C02 comprises an interface for receiving encrypted messages orencrypted javascript object notation (JSON) messages. Processor 11C04comprises a processor for executing applications 11C06. Applications11C06 comprise a set of DCIAMS applications. Decryption application11C08 comprises an application for decrypting encrypted data using akey. Login application 11C10 comprises an application for receivinglogin information (e.g., username and password, a credential, a QR codechallenge, etc.) and providing login credentials (e.g., a login token).Ledger interface application 11C12 comprises an application forinteracting with a distributed ledger (e.g., distributed ledger 11A04 ofFIG. 11A). For example ledger interface application 11C12 comprises anapplication for verifying a signature in a ledger or checking acredential identifier for revocation in a ledger. Proof requestapplication 11C14 comprises an application for creating a proof request,sending a proof request, evaluating a proof request response (e.g., aproof response), etc. Token generation application 11C16 comprises anapplication for generating a login token (e.g., in response to asuccessful login). Credential issuing application 11C18 comprises anapplication for issuing a digital credential for proving a qualificationin response to a request from a credential issuing authority to issuethe credential. Applications 11C06 additionally comprise any otherappropriate applications.

For example, processor 11C04 comprises a processor for receiving anindication of a new guest associated with an email address, receiving acreate indication to create a location aware credential representing alocation sensitive visitor permission associated with the guest,creating the location aware credential for the guest associated with theemail address, a user identifier (ID), and/or a user account, receivinga claim indication from an authentication device to claim the locationaware credential, determining whether the authentication device isassociated with the location aware credential, and in the event it isdetermined that the authentication device is associated with thelocation aware credential, providing the location aware credential tothe authentication device. Processor 11C04 additionally comprises aprocessor for receiving a check in indication to check in from anauthentication device, providing a proof request to the authenticationdevice, receiving a proof response, determining whether the proofresponse is valid using a distributed ledger, and in the event it isdetermined that the proof response is valid, providing a successindication of a successful check in and providing a location specificmessage.

Storage 11C20 comprises user and device database 11C22 and credentialrules 11C24. User and device database 11C22 comprises a database ofregistered users for a given customer organization and user details(e.g., username, password hash, contact information, email address,relationship to devices, registered public keys, registered mappingdocuments in a distributed ledger, etc.). User and device database 11C22additionally comprises a device directory comprising all the devices fora given customer organization as well as mapping documents associatedwith the devices and relationships with users associated with thedevices. Credential rules 11C24 comprises a set of credential rules fordetermining a credential that satisfies a given access request - forexample, rules related to a credential associated schema, a credentialassociated organization, a credential issuer, a credential associatedlocation, a credential associated class identifier, a credentialassociated license number, or any other appropriate credential rules. Invarious embodiments, rules comprise rules related to a credentialassociated schema, rules related to a credential associatedorganization, rules related to a credential issuer, rules related to acredential associated location, rules related to a credential associatedclass identifier or identifier number, rules related to a credentialassociated license or license number, a credential associated classname, or any other appropriate credential rules. In some embodiments,the rules are applied selectively (e.g., based at least in part on auser identifier)—for example, employees with a credential can accessapplication A, contractors with a credential can access application B,or any other appropriate matching of access with identifiers. In variousembodiments, the rules are applied selectively based at least in part oncurrent employment, employee type, location of user, qualification bytraining class, credential from a third party issuer (e.g., division ofmotor vehicle license, certification from school, etc.), or any otherappropriate criterion. As examples of configurable credential rules togrant access: 1) access is granted in the event that a credentialindicates that the holder is a current employee (e.g., issuing companyis valid, employee status is not expired, and not revoked); 2) access isgranted in the event that a credential indicates that the holder is anemployee in an organization of the company (e.g., issuing company isvalid, organization is specified organization, employee status is notexpired, and not revoked); 3) access is granted in the event that acredential indicates that the holder is an employee in a specifiedlocation (e.g., issuing company is valid, location is a specifiedlocation, employee status is not expired, and not revoked); 4) access isgranted in the event that a credential indicates that the holder hasnecessary training (e.g., issuing company is valid, training status iscomplete, employee status is not expired, and not revoked); and 5)access is granted in the event that a credential indicates that theholder has outside credential (e.g., issuing company is valid, outsidecredential is valid, outside credential issuer is third party, employeestatus is not expired, and not revoked). DCIAMS 11C00 additionallycomprises memory 11C26. Memory 11C26 comprises executing applicationdata 11C28, comprising data associated with applications 11C06.

FIG. 11D is a flow diagram illustrating an embodiment of a process forpreparing an authentication device for credential authentication. Insome embodiments, the process of FIG. 11D is executed by authenticationdevice 11A02 of FIG. 11A. In the example shown, in 11D00, an indicationto install a digital identity app is received. For example, theindication to install a digital identity app is received as part of ahuman resources system guest setup process. In 11D02, the digitalidentity app is installed. In 11D04, the digital identity app isassociated with a user. For example, the digital identity app isassociated with a user using a user email address, a user ID, and/or auser account. For example, a human resources system guest setup processprovides a one-time use token (e.g., a hypertext link) delivered to theemail address associated with the user. When the user invokes the linkon a computer (e.g., a laptop or desktop computer) the user is provideda quick response (QR) code for access by the authentication device. Whenthe authentication device accesses the QR code using the digitalidentity app, the digital identity app becomes associated with the useremail address. In some embodiments, the claim indication from theauthentication device to claim the location aware credential comprise aone-time token being used that causes generation of a DID keypair,wherein the private key component is stored on the authentication deviceand the public key component is stored on the distributed ledger, andthat causes providing the guest credential to the authentication device.In the event the user invokes the link using the digital identity app,the token is pushed into the mobile context to associate the digitalidentity app with the user email address. In 11D06, the user isregistered with a distributed ledger. For example, a user, useridentifier, or user account associated with the email address isregistered with a distributed ledger—for example, by invoking a linkthat has been delivered to the email address, scanning a QR code,registering a DID (e.g., a decentralized identifier) in a distributedledger, associating the DID with a guest credential, etc. In 11D08, aclaim indication is provided to claim a location aware credential fromthe DCIAMS, wherein the claim indication is associated with the user.For example, the location aware credential is only valid in a specificlocation, within a specific region, etc. In 11D10, it is determinedwhether the DCIAMS responds. In the event it is determined that theDCIAMS does not respond, the process ends. In the event it is determinedthat the DCIAMS responds, control passes to 11D12. In 11D12, thelocation aware credential is received from the DCIAMS. In 11D14, alocation detection system is activated (e.g., in order to determine whenthe authentication device is in a location where the location awarecredential is valid).

FIG. 11E is a flow diagram illustrating an embodiment of a process forpreparing a DCIAMS for credential authentication. In some embodiments,the process of FIG. 11E is executed by DCIAMS 11A06 of FIG. 11A. In theexample shown, in 11E00, an indication is received of a new guestassociated with an email address. In 11E02, a create indication tocreate a location aware credential representing a location sensitivevisitor permission associated with the guest is received. For example,the create indication is provided to the DCIAMS by a human resourcessystem employee setup process (e.g., a location aware credential iscreated for a guest as part of setting up the guest in the humanresources system). For example, the create indication is associated withan email address, a user ID, and/or a user account. The credentialspecifies visit location data (e.g., a location, a set of locations, alatitude and longitude, a region, etc. wherein the credential is valid).In 11E04, the location aware credential is created for the guestassociated with a user. In 11E06, a claim indication is received from anauthentication device to claim the location aware credential. In 11E08,it is determined whether the authentication device is associated withthe location aware credential. For example, determining whether theauthentication device is associated with the location aware credentialcomprises determining whether the email address, the user ID (e.g., anIKP), and/or user account associated with the location aware credentialmatches information (e.g., an identifier in the DID document) registeredin a distributed ledger. In the event it is determined that theauthentication device is not associated with the location awarecredential, the process ends. In the event it is determined that theauthentication device is associated with the location aware credential,control passes to 11E10. In 11E10, the location aware credential isprovided to the authentication device.

FIG. 11F is a flow diagram illustrating an embodiment of a process forcheck in. In some embodiments, the process of FIG. 11F is executed byauthentication device 11A02 of FIG. 11A. In the example shown, in 11F00,a detected location is detected using a location detection system. Forexample, an authentication device is periodically running locationservices (e.g., detecting a location using a GPS, say every minute) theauthentication device holds a location aware credential that is notexpired. In 11F02, it is determined whether the detected location iswithin a geographic boundary. For example, the geographic boundarycomprises a distance from a location in the visit location dataspecified in a location aware credential, a user-defined geofence (e.g.,specified by a system administrator, a human resources administrator,etc.), etc. In various embodiments, the visit location data includes acomplete specification of the location, a distance or radius around alocation, a geofence definition encompassing a location, a geographicboundary, or any other appropriate location data. In the event it isdetermined that the detected location is not within a geographicboundary, the process ends. In the event it is determined that thedetected location is within a geographic boundary, control passes to11F04. In 11F04, it is determined whether a location aware credential isnot expired at the current time. In some embodiments, determiningwhether a location aware credential is not expired at the current timecomprises determining whether the location aware credential is notexpired on the current day and/or date. In some embodiments, the checkin indication to check in additionally is in response to determiningthat the location aware credential is valid at a current time or for acurrent date. In the event it is determined that the location awarecredential is expired at the current time, the process ends. In theevent it is determined that the location aware credential is not expiredat the current time, control passes to 11F06. In 11F06, a check inprompt is provided to a user. For example, a check in prompt comprisesinformation for the user (e.g., a host location to meet a host or abadge location to receive guest identification). In 11F08, it isdetermined whether the user accepts the prompt to check in. In the eventit is determined that the user does not accept the prompt to check in,the process ends. In the event it is determined that the user acceptsthe prompt to check in, control passes to 11F10. In 11F10, an indicationis provided to a DCIAMS to check in. In 11F12, a proof request isreceived from the DCIAMS. In 11F14, a proof response is provided to theDCIAMS. For example, the proof response comprises the location awarecredential. In 11F16, it is determined whether the DCIAMS responds. Inthe event it is determined that the DCIAMS does not respond, the processends. In the event it is determined that the DCIAMS responds, controlpasses to 11F18. In 11F18, a success indication is received. In 11F20, alocation specific message is received.

FIG. 11G is a flow diagram illustrating an embodiment of a process forcredential authentication. In some embodiments, the process of FIG. 11Gis executed by DCIAMS 11A06 of FIG. 11A. In the example shown, in 11G00,a check in indication to check in is received from an authenticationdevice. In 11G02, a proof request is provided to the authenticationdevice. In 11G04, a proof response is received. In 11G06, it isdetermined whether the proof response is valid. For example, the guestcredential is checked against information stored in the distributedledger to determine whether the guest credential is valid—for example,has an appropriate schema, has an appropriate definition, is notexpired, and/or is not revoked. In the event it is determined that theproof response is valid, control passes to 11G08. In 11G08, a successindication of a successful check in is provided. For example, thesuccess indication of a successful check in is provided to a visitortracking system, to a visitor host, to the authentication device, etc.In 11G10, a location specific message is provided.

FIG. 11H is a flow diagram illustrating an embodiment of a process fordetermining whether a proof response is valid. In some embodiments, theprocess of FIG. 11H implements 11G06 of FIG. 11G. In the example shown,in 11H00, a DID document is retrieved from a distributed ledger based ona target DID in the proof response. In 11H02, it is determined whether apublic key from a distributed ledger matches a DID (e.g., adecentralized identifier) in a location aware credential (e.g., thelocation aware credential of the proof response). In the event it isdetermined that a public key from a distributed ledger does not match aDID in the location aware credential, control passes to 11H14. In theevent it is determined in 11H02 that that a public key from adistributed ledger matches a DID in the location aware credential,control passes to 11H04. In 11H04, it is determined whether the locationaware credential is satisfactory to authenticate check in. For example,determining whether the location aware credential is satisfactory toauthenticate check in comprises determining whether the location awarecredential is on a list of location aware credentials certified forcheck in, determining whether the visitor associated with the locationaware credential is scheduled to visit, determining whether the visitorassociated with the location aware credential has an employeeauthorization to visit, etc. In the event it is determined that thelocation aware credential is not satisfactory to authenticate check in,control passes to 11H14. In the event it is determined in 11H04 that thelocation aware credential is satisfactory to authenticate check in,control passes to 11H06. In 11H06, it is determined whether the locationaware credential is expired. In the event it is determined that thelocation aware credential is expired, control passes to 11H14. In theevent it is determined in 11H06 that the location aware credential isnot expired, control passes to 11H08. In 11H08, it is determined whetherthe location aware credential signature is valid. For example, thevisitor network credential signature comprises a signature from thecredential issuer (e.g., a DCIAMS) or from the credential holder (e.g.,the authentication device). In the event it is determined that thelocation aware credential signature is not valid, control passes to11H14. In the event it is determined in 11H08 that the location awarecredential signature is valid, control passes to 11H10. In 11H10, it isdetermined whether the location aware credential is revoked. Forexample, determining whether the location aware credential is revokedcomprises querying a revocation registry of a distributed ledger (e.g.,a decentralized ledger, a permissioned ledger, a public ledger, ablockchain, etc.). In the event it is determined that the location awarecredential is revoked, control passes to 11H14. In the event it isdetermined that the location aware credential is not revoked, controlpasses to 11H12. In 11H12, the process indicates that the proof responseis valid, and the process ends. In 11H14, the process indicates that theproof response is not valid, and the process ends.

FIG. 111 is a flow diagram illustrating an embodiment of a process forproviding a location specific message. In some embodiments, the processof FIG. 111 implements 11G10. In the example shown, in 11100, a locationrule is determined. For example, a location rule comprises a homelocation rule (e.g., is this location the user home location), a recentlocations rule (e.g., what other locations has the user been torecently), an unusual location rule (e.g., is this an unusual locationfor the user), etc. In 1102, it is determined whether the location ruleis satisfied. In the event the location rule is not satisfied, theprocess ends. In the event the location rule is satisfied, a locationspecific message is determined. For example, a location specific messagecomprises emergency information, local point of contact information,local destination information, etc. In 11106, the location specificmessage is provided to the authentication device.

A system for credential authentication comprises an interface configuredto receive a create indication to create a location aware credential,wherein the credential specifies visit location data and receive a checkin indication to check in from an authentication device, wherein theauthentication device provides the check in indication to check in inresponse to determining that a detected location is within a geographicboundary designated in the visit location data of the location awarecredential, and a processor configured to provide a proof request,receive a proof response, validate the proof response using adistributed ledger, and provide a success indication of successful checkin. In some embodiments, the interface is further configured to receivea claim indication from the authentication device to claim the locationaware credential. In some embodiments, the authentication device isconfigured to activate a location detection system upon claiming thelocation aware credential, wherein the detected location is measured bythe location detection system of the authentication device and ismonitored by the authentication device to determine when to provide thecheck in indication to check in. In some embodiments, the authenticationdevice provides a check in indication only in response to holding alocation aware credential that is not expired at a current time or for acurrent date. In some embodiments, the visit location data comprises alatitude and a longitude. In some embodiments, the location awarecredential comprises a set of locations. In some embodiments, thedetected location is detected using a global positioning system. In someembodiments, the geographic boundary comprises a distance from alocation of the visitor location data specified by the location awarecredential. In some embodiments, the geographic boundary comprises auser-defined geofence. In some embodiments, the authentication deviceprovides the check in indication to check in after an accepted userprompt to check in. In some embodiments, the authentication deviceprompts a user to check in automatically in response to determining thatthe detected location is within the geographic boundary that isspecified in the visit location data of the location aware credentialthat is being held by the authentication device. In some embodiments,the user prompt additionally comprises a host location to meet a host ora badge location to receive guest identification. In some embodiments,the success indication of successful check in is provided to a visitortracking system or a visitor host. In some embodiments, the processor isadditionally configured to provide a location specific message to theauthentication system. In some embodiments, the location specificmessage comprises emergency information, local point of contactinformation, or local destination information. In some embodiment, theprocessor provides the location specific message in response to adetermination that a location rule is satisfied. In some embodiments,the location rule comprises a home location rule, a recent locationsrule, or a unusual location rule. In some embodiments, validating theproof response using the distributed ledger comprises determining that acredential associated with the proof response satisfies the proofrequest, determining that a proof response signature is valid,determining that a credential associated with the proof response is notexpired, or determining that a credential associated with the proofresponse is not revoked by looking in the distributed ledger.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system for credential authentication,comprising: an interface configured to: receive a create indication tocreate a guest credential representing a guest badge associated with avisitor; and receive a claim indication from an authentication device toclaim the guest credential; and a processor configured to: provide theguest credential to the authentication device in response to the claimto indication; provide a proof request to the authentication device;receive a proof response from the authentication device; validate theproof response using a distributed ledger; determine a visitor trackingsystem associated with a request from the is authentication device toauthenticate entry; and provide a check-in indication to a visitortracking system that the visitor has checked in.
 2. The system of claim1, wherein the create indication to create a guest credential isassociated with an email address, a user ID, or a user account.
 3. Thesystem of claim 1, wherein the claim indication from the authenticationdevice to claim the guest credential comprises a one-time token beingused that causes generation of a DID keypair, wherein the private keycomponent is stored on the authentication device and the public keycomponent is stored on the distributed ledger, and that causes providingthe guest credential to the authentication device.
 4. The system ofclaim 1, wherein the processor is further configured to verify the guestcredential is associated with the authentication device.
 5. The systemof claim 4, wherein verifying the guest credential is associated withthe authentication device comprises comparing a guest credential emailaddress with an authentication device email address.
 6. The system ofclaim 1, wherein the proof request is provided in response to a requestto authenticate entry received from the authentication device.
 7. Thesystem of claim 6, wherein the request to authenticate entry is providedby the s authentication device in response to an authentication requestfrom the guest check-in site.
 8. The system of claim 7, wherein theauthentication request from the guest check-in site is provided inresponse to a check-in request from the authentication device.
 9. Thesystem of claim 8, wherein the check-in request from the authenticationdevice is provided automatically upon detection of proximity of theauthentication device to the guest check-in site.
 10. The system ofclaim 7, wherein the authentication device and the guest check-in sitecommunicate using a wireless protocol.
 11. The system of claim 10,wherein the wireless protocol comprises Bluetooth, NFC, or Zigbee. 12.The system of claim 6, wherein the request to authenticate entry fromthe authentication device comprises a check-in site identifier.
 13. Thesystem of claim 1, wherein the proof response comprises the guestcredential.
 14. The system of claim 1, wherein the proof response issigned with an authentication device private key.
 15. The system ofclaim 1, wherein validating the proof response using the distributedledger comprises determining that the guest credential is satisfactoryto authenticate check-in, determining that a guest credential signatureis valid, determining that the guest credential is not expired, ordetermining that the guest credential is not revoked by looking in thedistributed ledger.
 16. The system of claim 1, wherein validating theproof response comprises determining that the visitor has a scheduledappointment or an employee authorization to enter.
 17. The system ofclaim 1, wherein the create indication to create a guest credential isprovided by a human resources system guest setup process.
 18. The systemof claim 1, wherein the claim indication from an authentication deviceto claim the guest credential is provided in response to anauthentication device digital identification app setup.
 19. The systemof claim 18, wherein the authentication device digital identificationapp setup is in response to an email sent as part of a human resourcessystem guest setup process.
 20. A method for credential authentication,comprising: receiving a create indication to create a guest credentialrepresenting a guest badge associated with a visitor; receiving a claimindication from an authentication device to claim the guest credential;providing, using a processor, the guest credential to the authenticationdevice in response to the claim indication; providing a proof request tothe authentication device; receiving a proof response from theauthentication device; validating the proof response using a distributedledger; is determining a visitor tracking system associated with arequest from the authentication device to authenticate entry; andproviding a check-in indication to the visitor tracking system that thevisitor has checked in.
 21. A computer program product for credentialauthentication, the computer program product being embodied in anon-transitory computer readable storage medium and comprising computerinstructions for: receiving a create indication to create a guestcredential representing a guest badge associated with a visitor;receiving a claim indication from an authentication device to claim theguest credential; providing the guest credential to the authenticationdevice in response to the claim indication; providing a proof request tothe authentication device; receiving a proof response from theauthentication device; validating the proof response using a distributedledger; determining a visitor tracking system associated with a requestfrom the authentication device to authenticate entry; and providing acheck-in indication to the visitor tracking system that the visitor haschecked in.